I endorse the words, I currently implement some new test for https://issues.apache.org/jira/browse/OFBIZ-6988, and after 3 hours to build ofbiz, it's really boring without clear most valuable.
If for technical best practice it's better to keep test compile, it's possible when you test write is terminate to move the groovy-test-suite to junit-test-suite, so no reason to remove the possibility to write test as script. Nicolas On 08/09/2021 15:30, Gil Portenseigne wrote: > Hello, > > Currently using release 18.12 for some project we got the habit to > develop using integration test while developing in groovy. > > For that usage we use mainly : > groovy-test-suite > > That allow coding tests in groovy script that do not need to be compiled > for their execution and executing them from webtools [1] (small > improvement will be contributed soon), there is no need to reboot the > local dev OFBiz instance for each modification in that test. > > But these type of test has been removed with OFBIZ-11165 [2], while I > thinks that these resources are better compiled, during development > process, not having to restart OFBiz is nice. > > So if nobody is against, I will reintroduce it in trunk with a note > explaining the `dev` usage. > > WDYT > > Regards, > > Gil > > [1] https://localhost:8443/webtools/control/TestSuiteInfo > [2] https://issues.apache.org/jira/browse/OFBIZ-11165
