[
https://issues.apache.org/jira/browse/OFBIZ-12985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834264#comment-17834264
]
Jacques Le Roux edited comment on OFBIZ-12985 at 4/5/24 11:40 AM:
------------------------------------------------------------------
The idea is to create a subtask by component and to assign it to persons
working on it w/ coordination. Because files must be renamed (moved actually)
and that could be troublesome if several persons are working w/o coordination
(ie push, pull, revert, etc. vicious circle) .
was (Author: jacques.le.roux):
The idea is to create a subtasks by component and to assign it to persons
working on it w/ coordination. Because files must be renamed (moved actually)
and that could be troublesome if several persons are working w/o coordination
(ie push, pull, revert, etc. vicious circle) .
> Integration Groovy tests fail
> -----------------------------
>
> Key: OFBIZ-12985
> URL: https://issues.apache.org/jira/browse/OFBIZ-12985
> Project: OFBiz
> Issue Type: Bug
> Components: ALL APPLICATIONS, ALL PLUGINS
> Affects Versions: Upcoming Branch
> Reporter: Jacques Le Roux
> Priority: Blocker
> Fix For: Upcoming Branch
>
>
> Groovy testIntegration, tests suites and tests cases no longer work
> For my own help here is a simple case to test
> bq. "ofbiz --test component=accounting --test suitename=invoicetests --test
> testcase=invoice-per-shipment-tests"
> It seems testIntegrations work but when you look at the log you find a lot of
> (46, barely same than number of files: 44, did not digg more) "Unable to load
> test suite class" errors like this 1st one:
> {noformat}
> |ModelTestSuite|E|Unable to load test suite class :
> org.apache.ofbiz.party.PartyTests|
> {noformat}
> You can find that in last ofbizTrunkFrameworkPlugins BB build:
> [https://ci2.apache.org/#/builders/46/builds/777]
> The result seems successful. It's a misleading testIntegration result (not
> sure what does that) and an already old one. TestIntegrations still work in
> 18.12 and the issue is somehow related to OFBIZ-12813.
> It's a really confusing situation. Several issues prevent Groovy tests to
> work.
> The reason is due to wrong Groovy tests package names and locations due to
> OFBIZ-12813
> If we refer to our way of naming packages they are correctly referenced in
> testdef (eg org.apache.ofbiz.accounting vs org.apache.accounting.accounting)
> So it's only a simple packages names and locations changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
