Community
Participate
Working Groups
Build Identifier: I20100608-0911 I’ve been setting up headless tests for equinox based projects, and used ETF to do so; and, for a given project I had a requirement to be able to launch several tests in several fragments and I ran into the following use case Example : project.A is the host plugin of the fragment project.A.test ; which has a test suite TestSuiteA referencing several tests. project.B is the host plugin of the fragment project.B.test ; which has a test suite TestSuiteB referencing several other tests. In this particular case, if I use ETF as is (3.3.100)to launch those 2 test suites, I have to create a plugin test (projectC) referencing those 2 test suites. If I do so, then the test suite in projectC will not be able to access project.A.test and project.B.test testsuites; because fragments can not export their own packages... To make it work, I have then to transfoem project.A.test and project.B.test into plugin tests; but if I do so I have to export the packages containing the classes under tests in projectA and projectB --> and sometimes, it’s not a good idea to export packages; even more if the classes inside are supposed to be internal classes... Reproducible: Always Steps to Reproduce: See details for full use case
Created attachment 183427 [details] enables ETF to run multiple test suites, acrosss multiple test fragments So I decided to come up with this patch, allowing the user to launch in the runtime several testsuites for several fragments. You can launch it this way : Java –jar eclipse/plugins/launcher*.jar –application org.eclipse.test.coretestapplication formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,C:\tmp\results -testpluginsnames com.compuware.etf.hello.test,com.compuware.etf.goodbye.test -classesnames com.compuware.etf.hello.AllTests,com.compuware.etf.goodbye.AllTests -noExit -console You will notice •that I give in the formatter a directory to receive the results (instead of an XML file; because each test suites will have its own xml results file) •the new –testpluginsnames •the new -classesnames The cool thing about this change is that it does not break the older builds using the conventional ETF syntax. I’ve also been thinking about making ETF able to auto discover test suites in a runtime, so that we would need no configuration at.
Since this patch is greater than 250 lines, I opened an ipzilla to allow the Eclipse foundation legal department to review it https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4657
Created attachment 183621 [details] enables ETF to run multiple test suites, acrosss multiple test fragments --NO FORMATTING ISSUE Hello, The patch I submitted last week was longer than 250 lines because of formatting issue (I let my IDE reformat all the class). Now I recreated the patch, without the extra lines due to formatting, it's about 150 lines long. Sorry for the time spent because of this error...
Thanks for the contribution. I ran a test build with this today and our tests seemed to run fine. This has been released for N20101123-2000.
I've seen the change in HEAD: it is missing the copyright info in the header along these lines: Your Name <email@example.com> - Bug Title - https://bugs.eclipse.org/BUG_NUMBER
Created attachment 183757 [details] patch to update copyright
Created attachment 183758 [details] mylyn/context/zip
Tagged for next i-build. Thanks for the contribution to eclipse!
Thank you for reviewing this patch ! Will it be available through a p2 repo ? Thanks again !
Yes, the org.eclipse.test bundle will be available in our 3.7 stream update sites, starting with the nightl build tonight. http://wiki.eclipse.org/Eclipse_Project_Update_Sites
