Executing JLin Tests

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.

JLinEE tests are a special case. We recommend an alternative way of executing these.

More information: Executing JLinEE Tests

Creating and Running a Launch Configuration

1. In the menu bar, choose Run → Open Run Dialog…
2. Select JLin.
3. In the context menu of JLin, choose New.
4. In the Name field, enter a name for the configuration.
5. Select the sources to be tested - either Java Element or Working Set.
   • If you select the Java Element radio button, you choose project, source root, package, or class to be tested.
   • If you select the Working Set radio button, you specify one of the following: Window Working Sets, No Working Sets, or Selected Working Sets.
6. In the Variant field, select 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. In the context menu of the selected source files, packages, or projects, choose Run As → JLin.
3. Select a variant.
4. Choose OK.

Running JLin Automatically During Project Build

1. In the menu bar, choose Project  → Build Automatically.
2. SAP NetWeaver Developer Studio builds incrementally, that is, it builds only changes. JLin will be run only for the changed resources.
3. In the Package Explorer view, select the project that you want to test and choose Properties from the context menu.
4. Select Run JLin during build and select the variant.
5. Choose Apply and then OK.