Community
Participate
Working Groups
The objective wouldn't be to test the code, but just make sure the build process was at least mostly correct. The following are some examples: Test to be sure number of bundles is greater than or equal to previous number built. check that each bundle has an about.html file, a plugin.properties, file (and/or anything else that each plugin must have). Test to be sure the bundle can at least be activated.
I have created a new project org.eclipse.orbit.releng.tests and released it to the repository. Currently it contains code which accepts a configuration file containing regular expressions for the files which are expected to be in the bundles. Still need a good way to pass in arguments. (like input dir) The act of running the test is not currently hooked into the build.
*** Bug 189719 has been marked as a duplicate of this bug. ***
Tests re-enabled and released. See bug 206681 for future enhancements. Closing.