Executing Tests
Use
You can create a reusable launch configuration that will test all the sources in a single project or package, or test a single class. Alternatively, you can select any combination of sources from the Package Explorer view for immediate testing. In either case, you can also have JLin test only the ones that are editable.
You can have JLin execute during project build. The first time this option is enabled for a project, a full build and test is executed. Thereafter, during incremental builds, only the affected sources are tested.
J2EE tests are a special case. We recommend an alternative way of executing these. See J2EE Tests with JLin.
Procedure
Creating and Running a Launch Configuration
1. Choose Run → Run…
2. In the Configurations pane, select JLin.
3. Choose New.
4. In the Name field, enter a name for the configuration.
5. Select the sources to be tested – either Java Element (project, source root, package, or class) or Working Set.
6. In the Variant field, enter the variant to be executed.
7. Choose Apply.
8. Choose Run.
Package Explorer
1. In the Package Explorer view, select the source files, packages, or projects that you want to test.
2. Choose Run → JLin.
3. Select a variant.
4. Choose OK.
Running JLin Automatically During Project Build
...
1. Choose Project → Build Automatically.
Eclipse builds incrementally – that is, it builds only changes. JLin will be run only for the changed resources.
2. In the Package Explorer view, select the project that you want to test and choose Properties from the context menu.
3. Select Run JLin during build and choose the variant.
Result
When the variant has finished executing, you will get a summary consisting of the total number of messages and the number of messages in each priority category.
The results are then displayed in the Problems view.
See also: