> Just list a few Gradle commands that should be tried. I really recommend installing https://github.com/dougborg/gdub though to shorten ./gradlew to gw and enable running gw from any directory of the project.
./gradlew clean ./gradlew createDist # currently it tries to copy build artifacts to root lib/ folder so JMeter is startable. ./gradlew check # to run all the tests ./gradlew createDist --parallel # to run all the tasks in parallel ./gradlew -x test createDist # to build but skip tests ./gradlew :src:core:check # run tests for "core" module ./gradlew check # run tests for "core" module ./gradlew :src:functions:test --tests org.apache.jmeter.functions.ChangeCaseSpec # run a single test class in "functions" Module However, I don't really expect Gradle commands to be used extensively besides clean / build / check. sebb> Not sure what build script you are referring to. sebb> Does it create the jars, or just the classes? Of course it does. It even creates separate jars with test classes. sebb> Which IDEs have you tried? IntelliJ IDEA 2019.1 EAP sebb> Are these 'more tests' new tests, or do you mean tests which have not sebb> been transferred from the Ant build and need to be created? Anything. Any kind of experiments would help to see if development with Gradle feels right or not. sebb> How does Gradle know what the required commands are? sebb> Don't you have to tell it? No, I don't. It just analyzes build script and it knows which modules it needs to recompile and which are fine. sebb> fix the problem, though it may well be easier to specify the sebb> pre-requisites. It does fix the problem. For instance, current "ant junit single class run" target does not know it should build the jars before running the test. Apparently certain tests depend on having up to date JARs. Ant output does not help to understand that. Do you know "ant junit" is not documented? It takes considerable efforts to just run the test with Ant. Vladimir
