3.2 RC2 Test Grid

Goal

• verify features and bug fixes done for RC1 and RC2
  

Verification of Bugs (ALL - this one has to be done first)

• Platform Text, Search, and Compare bugs blocker/critical/major, 3.2 RC1 + RC2
• Platform Text, Search, and Compare bugs P1/P2, 3.2 RC1 + RC2

• JDT Text & JDT UI bugs blocker/critical/major, 3.2 RC1 + RC2
• JDT Text & JDT UI bugs P1/P2, 3.2 RC1 + RC2

Content Assist (Markus, Johannes)

• Additional Info

1. Try code assist and verify the additional info pops up with
   - attached javadoc (remote, local, dead remote web-server..., no internet)
   - attached source
   - nothing
2. Verify correct size and position of the additional info popup
   - at all sides of the proposal popup (right, left, bottom)
   - after resizing the proposal popup (on win32)
   

• Parameter Hints

1. Try parameter hints display
   - visibility (show when a proposal is applied, hide when caret goes outside the parentheses)
   - parameter highlighting
2. Try with method arguments that contain commas and parentheses:
   - array initializers
   - anonymous type creations
   - generic class instance creations

Sticky Ruler Hovers (Benno, Tobias)

• Hover over annotations in the left-hand-side ruler of the Java editor:
  - problem annotation hovers
  - projection hovers
  - quick diff hovers
  - live annotate hovers
  

• when the editor has focus: press F2 to make the hovers sticky

Hover and Hyperlink Precsission (Martin, Tom)

• test that the hovers and hyperlink activation is correctly at word/identifier bounds

JUnit 4 (Tobias, Martin)

- launch JUnit 3.8.1 and JUnit 4 tests
- JUnit test case wizard
- quick fix when JUnit library is missing on build path

Menu polish: (Dani, Markus)

• test 'Copy Qualified Name' action
• test enablement
• test result
• test 'Surround With' quick menu and actions
• test enablement
• test result
• test that 'Find Occurrences' quick menu still works as before
• All 'History' actions in the view menu (Search, Type Hierarchy, Call Hierarchy, JUnit) have been made consistent.
  

Search (Tom, Dani)

- Text search: Work on performance and better presentation of progress
- File Name Pattern Exclusion, bug 134627

Stress test refactoring scripting (Johannes, Benno)

• Test Replace JAR with various project setups: JAR within client project, JAR within workspace, external JAR in filesystem
  - verify that refactorings can be successfully executed
  - verify that refactoring preview only shows changes to be applied to the client project, and not the JAR on the build path
• Test creating and applying refactoring scripts
  - verify that all generated scripts can be successfully executed on other workspaces (given the input elements of the refactorings exist in the other workspace as well)
• play through the refactoring script scenario (perform a refactoring, save it as script and reapply it)
• play through the JAR with exports scenario (perform a refactoring, save JAR with refactoring, replace old JAR with new JAR (build
  
• verify updated dialogs: History, JAR exporter
• try all refactorings and check if the labels in the history view make sense