Juno M3 Test Plan

Setup

Builds

• 3.8 build: Markus and Dani
• 4.2 build: Raksha

Platforms

• Windows 7: Dani, Raksha
• Linux-GTK: -
• Mac OS X 10.7: Markus

Goal

• test new functionality added since M2
• verify that severe bugs are correctly fixed

Test New Functionality

Associate editor to class files without source (Raksha, Markus - Questions: Dani)

• verify that out of the box our Class File editor appears
• verify that the association appears on the preference page
• verify that an associated internal editor opens for class files without source
• verify that an associated external editor opens for class files without source
• verify that always our Class File editor opens when source is available

Output location overlapping source folder problem detection (Markus, Raksha - Questions: Dani)

• verify that out of the box it is not possible to create such a setup
• set the severity to 'Warning' and verify that one can now setup such a project
• now verify that we report a warning on such a project
• set the severity to 'Ignore' and verify that one can now setup such a project
• now verify that we do not report any warning on such a project
• verify all the above steps tomorrow in M20111026-0800

Preference to show annotations saturated in the Overview ruler (Dani, Markus - Questions: Raksha)

• test that out of the box the annotations appear as before
• verify that annotations are rendered with saturated colors if the preference is enabled
• test that editor updates when toggling the preference and pressing 'Apply'
• verify that the documentation (F1 in preference page) is available and accurate

Quick Assists to synchronize Java properties file and corresponding message class (Raksha, Dani - Questions: Deepak)

• test the 'Create field in ...' Quick Assist
• test the 'Rename in workspace' Quick Assist
• test the 'Remove key' Quick Assist

New warnings for resource leaks and missing try-with-resources (Dani, Raksha - Questions: Deepak)

• sanity check the wording of the new options
• test that the new options works (change to 'Ignore', 'Warning' and 'Error')
• try to break the Resource Leak and and Potential resource Leak warnings
  • check for false positives and/or incorrect warnings
  • check for cases where a warning is missing
  • check if the warnings are easy to understand (Hint: Resource is not closed at this location)
• factors that should be considered
  • resource object flows out of a method - as a parameter in a method call, as a return value, by assignment to a field
  • resource is not closed on all code paths - if and switch statements, try-finally blocks, try-catch blocks, try-catch-finally blocks etc
  • reassignment to another resource variable

Convert to enhanced for loop (Markus, Raksha - Questions: Deepak)

• let the clean up run on big projects and verify the results

Delete projects dialog shows project locations (Dani, Raksha - Questions: Markus)

• verify that the project location(s) are shown on the first wizard page
• verify that the project location(s) are shown on the preview page
• bonus points: try it with a project that is not on the local file system (if you know how to set this up)

Bug Verification (All)

• P1 JDT UI bugs, 3.8 M3
• P1 Text and Search bugs, 3.8 M3
• JDT UI bugs blocker/critical/major, 3.8 M3
• Text and Search bugs blocker/critical/major, 3.8 M3