3.1 M2 Test Grid

[Tom Eicher <eclipse@xxxxxxxxxxxxxxx>]

Here is the combined 3.1/M2 test plan for JDT UI, JDT Text, Platform Text, Platform Search and Platform Compare.

Testing will take place tomorrow (Wednesday, September 22) as stated on the M2 build schedule.

Feel free to send an email to the list or directly to me if you would like to join in for this test pass.

Tom

Title: ZRH 3.1-M2 Test Grid

3.1 M2 Test Grid

Wednesday, September 22, 2004
Also see the M2 build schedule

Components

This test grid covers the following components

• JDT UI
• Platform/JDT Text
• Platform Search
• Platform Compare

Goal

• test new functions added since M1
  
• sanity check performance
• verify that severe bugs are correctly fixed

Testers So Far

Everybody from the community is welcome to help with testing. Please
send a note to this list if you want to help testing the 3.1 M2
candidate.

• André
  
• Dani
• Erich?
  
• Kai
• Markus
• Tobias
• Tom

1.5 Features - UI

Test whether the following items work correctly, and whether switching
the source version of a project has the appropriate consequences (i.e. convert for loop only available in 1.5, but not in 1.4).

• "convert for loop" quick assist (bug 70922)
  
• Pull Up / Push Down refactorings for generic types
• new formatter settings for 1.5
• "Rename" refactoring for type parameters

New Quick Assists

• see bug 71244

1.5 Features - Editor

Test whether the following items work correctly, and whether switching
the source version of a project has the appropriate consequences (i.e.
enum is a keyword for 1.5, but not for 1.4).

• new keywords: enum, @interface
• highlighting of <> brackets when used to declare a type parameter list
• auto-insertion of the closing > bracket when typing a generic type name

Encoding

Verify the following works correctly:

• changing the encoding manually (over the property dialog)
• with auto-refresh enabled: external encoding change (e.g. the encoding spec of an XML file is changed using an external editor)
• Property dialog binding: test whether Alt+Enter or File->Properties is enabled when the editor has focus, and brings up the correct properties dialog.
  

Javadoc

Check:

• Auto-Indentation inside javadoc:
• at the beginning, inside, at the end of a javadoc line
• Auto-insertion of javadoc parameters (enable in preferences).. see bug 55325
  

Linked Mode

Linked mode has undergone some changes to avoid exiting when changes
occur somewhere in the document while the linked mode is active.

• Verify that templates work ok: linked mode should exit
• upon switching applications
• when typing outside an edit box
• when pressing ESC or ENTER (if no proposal popup is open - if there is one, it will close first)
• when pressing CTRL+ENTER
  
• Verify that if you import a Type while inside a template (for example the element type in a Collection - for-loop),
• the import gets added
• linked mode does not exit

Verification of 2 Bugs

Before starting to verify add a comment that you are taking the bug for verification.

• JDT UI major, critical and blocker but not P1 or P2 bugs tagged 3.0 M4 (2 bugs)