3.3 M2 Test Plan

Goal

• test new functionality added since 3.3 M2
  
• sanity check performance
• verify that severe bugs are correctly fixed

Verification of Bugs (ALL)

• JDT UI bugs P1/P2, 3.3 M2
• Platform Text, Search, and Compare bugs P1/P2, 3.3 M2
• JDT UI bugs blocker/critical/major, 3.3 M2
• Platform Text, Search, and Compare bugs blocker/critical/major, 3.3 M2

Live Annotate (Dani, Tobias - FAQ: Tom)

• test the different coloring schemes (via ruler context menu > Revisions)
  
• test textual information display in all combinations, assure that the alignment in the column is correct
• test the command support for coloring scheme toggling and information toggling (needs to be bound manually)
• test making a revision sticky (by clicking on it, or by selecting it in the history view)
• test to remove the stickiness (by clicking it again)

Pluggable Vertical Ruler Support (Markus, Benno - FAQ: Dani, Tom)

• test that existing rulers (vertical ruler, line number ruler and quick diff work as in R3.2
• test enablement behavior
• test hovers
• test clicking on annotations
• test context menu (are the same entries there? do they work as expected?)
• add a new example ruler to a new editor that inherits from AbstractTextEditor but not from AbstractDecoratedTextEditor using the extension point doc as start

Clean Up Profiles (Martin, Dani - FAQ: Benno)

• clean up projects with workspace settings
• clean up projects with project settings
• clean up projects with workspace/project settings
• import/export clean up profiles
  

Clean Up Formatting (Tobias, Martin- FAQ: Benno)

• test code and comment formatting through clean up
• test formatting in combination with other clean ups

• verify that the correct disassembled code is shown (compare using javap)
• verify that long content is correctly displayed
• verify that keyboard navigation (e.g. Page Up/Down) works

• verify that a warning dialog appears when editing a derived file
• verify that the checkbox in the dialog works
  
• verify that this feature can be configured via General > Editors > Text Editors > Warn before editing a derived file preference
• verify that the preference is coupled with the checkbox on the warning dialog
  

• verify that Ctrl+L triggers the Recenter command when using Emacs scheme

Lightweight Rename (Tom, Dani - FAQ: Markus)

• enable in Preferences > Java > Refactoring Java Code > Show Rename refactoring in editor

Polymorphic method reference search filter (Tom, Benno) - FAQ: Markus)

• see bugs 156491, 73401
• should filter out method references that point to methods that override / are overridden by the search target
  

JUnit launch shortcuts (Dani, Tobias - FAQ: Markus)

• verify that 'Run/Debug As > JUnit (Plug-in) Test' context menu items still work for JUnit 3 and JUnit 4 test methods, classes, packages, and source folders

Sanity check Project Navigator (Tom, Markus - FAQ: Martin)

• test the ported fixes from 3.2.1 to 3.3
• test e.g. working set mode, DND, action enablement

Property pages enablement (Tom, Dani - FAQ: Martin)

• verify that Java build path page and code style pages only shows up on projects with Java nature that are open
• verify that source attachment only on libraries and class folders
• verify that Javadoc location on projects, libraries and class folders
• verify that refactoring history only on projects with a history

Validate edit on package rename, and CU move and rename (Markus, Benno) - FAQ: Martin

• validate edit for moved files should only happen if the file is also modified (for example a package declaration is changed). No validate edit if a resource is just moved