| Re: [mdt-papyrus.dev] status of AllTests.java |
hey, I do understand your concern but I was not aware of your concern to run all the tests in a single workbench instance. I am not sure we could keep a manual procedure when we have a such big and complex project as papyrus. In order to run the tests of a plugin, you could execute them with maven. -directly from Eclipse but you need to maven nature -from command line by executing for instance: mvn clean install -f tests/junit/plugins/uml/profile/org.eclipse.papyrus.uml.profile.drafter.tests/pom.xml -Dpapyrus.repo.main=file:///export/home/flefevre/git/org.eclipse.papyrus/releng/main/site/target/repository/ -Dpapyrus.repo.dev=file:///export/home/flefevre/git/org.eclipse.papyrus/releng/dev/site/target/repository/ -DskipInnerTests=false This way to do is similar/identic to the one executing in eclipse HIPP instance. About the workbench instance, I have looked to https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html They are a lot of customization possible. When look at https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html , they explain that we could use parallel mode “When using reuseForks=true and a forkCount value larger than one, test classes are handed over to the forked process one-by-one. Thus, parallel=classes would not change anything. However, you can useparallel=methods: classes are executed in forkCount concurrent processes, each of the processes can then use threadCount threads to execute the methods of one class in parallel.” The option all seems good to me? Perhaps there is a way to execute all tests in a same workbench. I have tested at the level of one plugin: it executes only one workbench If we want to aggregate tests, as usual I would propose to make intermediate pom… See this bug: https://git.eclipse.org/r/#/c/50501/ ; https://git.eclipse.org/r/#/c/50503/ I didn’t get any answer… Do you think we should look more precisely to Tycho-surefire plugin? waiting additional information. Francois Here configuration for nattable test = 4 plugins grouped with one pom <plugins> <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>tycho-surefire-plugin</artifactId> <version>${tycho-version}</version> <configuration> <failIfNoTests>false</failIfNoTests> <useUIHarness>true</useUIHarness> <useUIThread>true</useUIThread> <testFailureIgnore>true</testFailureIgnore> <argLine>-Xms512m -Xmx2048m -XX:MaxPermSize=512M -XX:SoftRefLRUPolicyMSPerMB=100</argLine> <appArgLine>-testConfig=${testConfig}</appArgLine> <product>org.eclipse.sdk.ide</product> <skipTests>${skipInnerTests}</skipTests> <!-- run tests on a pool of 3 concurrent process --> <forkCount>2</forkCount> <!--or 0 --> <!-- use a pool of JVMs --> <reuseForks>true</reuseForks> </configuration> </plugin> </plugins> [INFO] Reactor Summary: [INFO] [INFO] org.eclipse.papyrus.uml.nattable.tests.main ........ SUCCESS [ 0.137 s] [INFO] org.eclipse.papyrus.uml.nattable.clazz.config.tests SUCCESS [ 2.663 s] [INFO] org.eclipse.papyrus.uml.nattable.generic.tests ..... SUCCESS [ 21.395 s] [INFO] org.eclipse.papyrus.uml.nattable.stereotype.display.tests SUCCESS [ 24.697 s] [INFO] org.eclipse.papyrus.uml.nattable.tests ............. SUCCESS [ 17.025 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:18 min [INFO] Finished at: 2015-07-02T18:07:53+02:00 [INFO] Final Memory: 76M/859M [INFO] ------------------------------------------------------------------------ De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus Hi, We have the suite-of-suites in the org.eclipse.papyrus.tests bundle in order to run all the tests in a single workbench instance. Will this change result in a workbench being launched for each test plug-in when run by Maven? That will add a lot of overhead (OS resources and time) to the test execution. And what does this mean for all of the launch configurations in every test project? And how will we launch tests in the Eclipse IDE? The JUnit launch config doesn’t look at the POM. Christian On Thu, Jul 2, 2015 at 10:36 AM, LE FEVRE FRANCOIS <francois.le-fevre@xxxxxx> wrote:
| ||||||||||||||||
Attachment:
smime.p7s
Description: S/MIME cryptographic signature