API Tools Project 3.6M5 Test Plan

Testers

Committers: Darin Wright, Michael Rennie, Olivier Thomann

Community: Anyone who wants to help

Test Grid

Feature Testing

API Tools Setup

  1. General
    • setup wizard should have a help topic
  2. Setup API Tooling
    • wizard with no selections in workspace and with selections; if the there are selected projects in the workspace that can have API tooling setup on them, they should be preselected in the wizard
    • try canceling the wizard
    • try selecting / unselecting all to make sure the finish and preview button work as expected
    • try selecting a project and viewing a preview
    • try selecting projects that do and do not have a component.xml file
    • ensure tags are added correctly to files (from the component.xml)

Back to top

API Baselines

  1. General
    • changing / editing / removing of the default baseline should ask you to build when the Ok button is pressed on the preference page
    • the page and wizard should have help topics
  2. Create a new API baseline
    • try completing the wizard and canceling it
    • try renaming a baseline (accepting and canceling the process)
    • try changing the location of the new baseline and resetting the profile
  3. Edit an API baseline
    • try completing the wizard and canceling it
    • try renaming a baseline (accepting and canceling the process)
  4. Deleting an API baseline
    • try deleting a baseline
    • try deleting select baselines
    • try deleting all baselines
  5. Default Baseline
    • try selecting a new default baseline
    • try editing the default baseline (rename, should still be the default after rename)
    • try deleting the default baseline
  6. Change the warning level for missing default baselines

Back to top

Building

  1. Full Build
    • Run a full build on one project
      • markers should be updated
      • filters should be respected
      • progress messages should be correct
      • time to build should be reasonable
    • Run a full build on the workspace
      • builder should only run on 'API aware' projects
      • markers should be updated
      • filters should be respected
      • progress messages should be correct
      • time to build should be reasonable
  2. Incremental Building
    • Change a dependent type
      • builder should run for dependent's
      • markers should be updated for dependent's
      • filters should be respected on type and dependent's
      • time to build should be reasonable

Back to top

Unsupported Javadoc Tags

Enable the check for unsupported Javadoc tag checking. All of the given tests should produce API problems, and all content assist-available tags should not

  1. add noimplement, no reference and nooverride tags to class (inner, outer, static, static inner, etc)
  2. add noinstantiate, noextend, noreference and nooverride tags to an interface (annotation)
  3. add noimplement, noextend and noinstantiate tags to a method
  4. add noimplement, noextend, noreference and noinstantiate tags to a constructor
  5. add noimplement, noextend, nooverride and noinstantiate tags to a field
  6. add noimplement, noextend, noreference, nooverride and noinstantiate tags to a final field

Back to top

Quick Fixes

All quick fixes should not put a project in a state of error, and should work with an existing modified editor (i.e. even if there are unsaved edits in the editor the quick-fix is being activated on)

  1. Usage problems
  2. Compatibility problems
  3. Version problems
  4. Since Tag problems
  5. API Leak problems

Back to top

Filters

  1. General
    • Property page should have a help topic
    • Remove button should enable / disable properly
  2. Add Filters
    • Use the quick fix
    • Drag & Drop in an existing filter file
    • Check out a filter file from CVS
    • First added filter should cause filter file to be created immediately
    • Other added filters should be written to filter file immediately
  3. Remove Filters
    • Use the property page
      • Try removing one or more filters by individually selecting filters or their parent file.
      • Ensure removed filters are removed (apply change or click Ok to close the property page, and reopen)
      • Canceling deleting filters should make no change
      • Removing filters should rebuild the project (incremental)
      • Removing last filter should remove the filter file immediately
    • Drag & Drop a filter file out of the project
    • Over-ride and update from CVS
    • Auto-remove using the builder preference

      A good test case: (1) start new workspace, (2) bring org.eclipse.ui.navigator from R3_5 branch (3) set baseline to an Eclipse 3.5.0 install.

      With the above set-up now change the setting in the workspace and the project and ensure filters are automatically cleaned up or reported depending on the setting.

  4. Share Filters
    • Commit filter to CVS and check it out in another workspace
    • Should update filtered problems on next rebuild (unless the filter store for the project in question is already loaded)
  5. Unused Filters
    • Create a filter for a Java element and them remove the element - problem should be reported
    • Create a filter for a Java element and delete the containing compilation unit - no problem (filters are cleaned up when the filter store is initialized / workspace restarted)
    • Quick-fix to remove the filter
    • Quick-fix to open the property page

Back to top

Preferences

  1. General
    • The API Errors/Warnings page should have a help topic
  2. Workspace
    • Change any number of preferences and apply the page (via the Apply button or the Ok button)
    • Change any number of preferences and hit 'Restore Default'
    • Change any number of preferences and cancel the page
    • Change all preferences using the 'Set all to' buttons (and apply / cancel / restore defaults)
    • Use the link to configure project specific settings
  3. Per-Project
    • Try turning project specific settings on / off
    • Change any number of preferences and apply the page (via the Apply button or the Ok button)
    • Change any number of preferences and hit 'Restore Default'
    • Change any number of preferences and cancel the page
    • Change all preferences using the 'Set all to' buttons (and apply / cancel / restore defaults)
    • Use the link to configure workspace settings

Back to top

Invalid System Library References

  1. 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

Back to top

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.

  1. Create / delete projects in your workspace
  2. Bring in projects from CVS
  3. Open / close projects
  4. Import projects (binary and normal projects)

Back to top

Run The Test Suite

  1. Run ApiToolsTestSuite
    • on Windows XP
    • on Windows Vista
    • on Linux
    • on Mac OS
  2. Run ApiToolsPluginTestSuite
    • on Windows XP
    • on Windows Vista
    • on Linux
    • on Mac OS

Back to top