3.2 M5 Test Grid

Goal

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

Verification of Bugs (ALL)

• JDT UI bugs P1/P2, 3.2M5
• Text, Search, and Compare bugs P1/P2, 3.2 M5

• JDT UI bugs blocker/critical/major, 3.2 M5
• Text, Search, and Compare bugs blocker/critical/major, 3.2 M5

• all JDT UI bugs 3.2 M5
• all Text, Search, and Compare bugs 3.2 M5

Watch out for cheese and odd behavior in the Text and Java editors (ALL)

New clean ups and new Clean Up Wizard UI (Markus, Tobias) (FAQ: Benno)

Check wording and test usability of new Clean Up Wizard

Test new Clean ups:

• Add serial version Id (generated/default)
• Remove unnecessary blocks
• Remove unnecessary casts

Build path wizards (Martin, Tom) (FAQ: Benno)

Test new build path wizards:

• Link source folder
• Add source folder
• Edit inclusion/exclusion patterns

• New Project creation wizard
• Package explorer context menu
• Projects build path properties

• Verify that there is no way to commit an invalide class path
• Check wording
• Test usability
• Test that renaming/removing/adding a source folder works as expected (i.e. that the corresponding files are removed/renamed/added as well)

Type selection history (Tom, Markus) (FAQ: Benno)

Import types with:

• Code assist
• Organize import
• Add imports

Verify that:

• Previous selected types are on top of the list if conflicting types
• Selection history is stored between sessions

Try to find dialogs where it would also make sense to have the same history

Package Explorer 1 (Dani, Benno) (FAQ: Dirk)

• test in workset mode
• create a couple of working sets having the same elements
• structurally change the content of the elements in the working set by adding, removing or moving elements.

Ensure that:

• no elements get lost or rendered more often than they should
• they are rendered under the correct parent
• the selection is kept stable during these changes

Package Explorer 2 (Dani, Martin) (FAQ: Benno)

Make sure that compilation units are never parsed while exploring the package explorer/resource navigator/java browsing perspective (unless of course the cu needs to be parsed because the cu is expaned)

• Take a large cu (3MB+) watch out for ui freezes
• Test in flat and hierarchical mode
• Open context menu on elements

See also bug 127105

Editors (Tobias, Markus) (FAQ: Dani)

• test Quick Fix in the Properties editor (via menu and via key binding)
• test whether Quick Fix works in the Properties editor (via menu and via key binding)
• test whether Quick Fix works in the Java editor (via menu and via key binding)
• compare two *.properties files - verify that the compare editor opens
• compare two *.java files - verify that the compare editor opens
• test 1 1/2 click in the text and Java editor
  
  note: selection is done character by character and not word by word

Read only status (Benno, Martin) (FAQ: Dani)

verify that the read-only status is correctly shown for:

• read-only *.java files
• *.class files
• types from a JAR

Generate hashCode() and equals() (Benno, Tom) (FAQ: Tobias)

• Verify that correct code is generated
• Verify that warning messages appear in a dialog if either:
  • the hashCode()/equals() is not implemented within the classhierarchy
  • or the generated would reference a field whose type has unimplemented hashCode()/equals() methods.

JAR Exporter (Markus, Martin) (FAQ: Tobias)

Test the export of JAR files with refactoring information

Verify that the checked refactorings are indeed exported (refactorings.xml in the META-INF directory)

Replace JAR File (Dani, Tom) (FAQ: Tobias)

• Test the replace of an existing JAR file on the build path with a new one containing refactoring information.
• Test replacing an existing JAR file which contains refactoring information with a new one containing the entire project history. The refactoring preview should only display the delta which has not yet been applied.

Refactoring Scripts (Dani, Benno) (FAQ: Tobias)

• Test the creation and application of arbitrary scripts, containing several refactorings
• Verify that correct undos are generated

JUnit View History (Tobias, Benno) (FAQ: Markus)

• test the view with concurrent JUnit Tests and JUnit Plug-in Tests
• test switching from/to running/stopped/finished test runs
• verify that progress is correctly reported in progress bar/counters
• check view icons (shows progress if view is invisible fast view; sensible image when view is visible)

Introduce Indirection (Tom, Dani) (FAQ: Markus)

• test with methods from source and with binary methods (start at an invocation site)
• test with overridden methods

Problems view (Tom, Tobias) (FAQ: Martin)

• Test problems view with grouping and sorting
• Test quick fix dialog
  • With and without multi quick fixes (all quick fixes which are also clean ups are multi quick fixes FAQ: Benno)

Search view (Markus, Dani) (FAQ: Martin)

template expansion (Benno, Martin) (FAQ: Tom)

see bug 126662 and 71587

• with different selections: none, single-line, multi-line
• invoke content assist on a selection, then type the name of the template to refine the proposal list
• check that formatting is ok

template import export (Tobias, Markus) (FAQ: Tom)

• import templates
• override the default using the -pluginInitialization command line switch
• ensure pressing the "Defaults" button on the preference page works as expected

content assist (Tobias, Martin) (FAQ: Tom)

see bug 49610 ensure that inserted completions (java methods, types) conform to the formatter preferences:

• method, type arguments
• parentheses, brackets...