Menu

#5 Use *.launch files in projects to launch JUnit tests

open
nobody
None
5
2010-10-22
2010-10-22
Mirko Raner
No

The current heuristic that ebuilder uses to decide whether to run a test project as regular JUnit tests or as JUnit plug-in tests may not return the correct test type under certain circumstances. Also, some tests may require customized launch configurations to run properly.
To address these issues, ebuilder should first search each project for *.launch files that contain JUnit or JUnit plug-in configurations. If one or more of such files are found those files should be used to run the tests. If no launch configuration is found ebuilder should fall back to heuristically generating the launch configurations.

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.