Invalid System Library References

change EE to 1.4 (or prior), set build-path JRE to be 1.5 or greater, and access types / methods / fields from the build path library

add / remove EE descriptions from the preference page

Target Platform Stability Workspace Baseline

These tests are to ensure there is no corruption to the target platform when performing workspace baseline changes during normal development. All of the following tests require that the Target Platform State view be open and that it be checked after each of the following tests to ensure no bundle problems arise.

create / delete projects in your workspace

bring in projects from CVS

open / close projects

import projects (binary and normal projects)

Use Scan Reference

API Use Scans

Test adding directory and archived API Use Scans

Test with adding invalid use scans (directory and archives)

Test Edit/Remove

Test that build is triggered after changes

Use Scan Preferences

Test setting preferences on API Use Scans tab of API Error/Warnings

Test with different severities for Type, Method and Field problems

Test that severity changes are reflected in markers in Problems view

Ant Task

Test running the apitooling.apiusescanproblems ant task

Test that it generates same problems as in the problems view

References

Test for missing Type, Method and Field

Test that missing method marker is placed at correct line numbers and are made on proper java file

Test that missing field marker is placed at correct line number and are made on proper java file

Test that missing type markers has line number as -1 and are made on Project

Run The Test Suite

The shared launch configurations in the org.eclipse.pde.api.tools.tests bundle can be used to run these