3.4 M4 Test Plan

Test day: Tuesday, 2007-12-11
Test Build: start with I20071210-1800 and switch to when available I20071211-0010
Components: Platform Search, Platform Text, JDT Text and JDT UI
Testers: Benno, Dani, Markus, Martin

Platforms

WindowsXP: Benno
WindowsVista: Martin
Linux GTK: Dani
Mac OS X: Markus

Goal

test new functionality added since 3.4 M3
verify that severe bugs are correctly fixed
sanity check performance

Test New Functionality

First test all those items where you are listed as first tester.

Test that rich hovers work doesn't break old behavior (all - FAQ: Dani)

While testing your items keep an eye on the hovers and also use F2 from time to time: this should work as usual. We need to make sure that the new rich hover code (which is still off) didn't break existing behavior.

Overview ruler improvements (Martin, Markus - FAQ: Dani)

Test the new overview ruler features:

hover shows line number when there's no annotation below
clicking when there's no annotation below goes to the correct line
check that the line it goes to when clicking is the same as shown in the hover
a context menu with one item ('Preferences...') is shown on right-click
verify that the 'Preferences...' menu item when no annotation is below opens the 'Annotations' preference page
verify that the 'Preferences...' menu item on an annotation opens the 'Annotations' preference page and selects the corresponding annotation type

Annotations can use any text style (Benno, Martin - FAQ: Dani)

Use the 'Annotations' preference page to test that:

for each annotation type verify that you can choose between all available text styles (should be 7)
for each annotation type verify that the defaults are still the same as in 3.4 M3
Note: there will be three exceptions: 'Errors', 'Warnings' and 'Spelling Errors' will now use 'Native Problem Underline'

New 'Native Problem Underline' text style (Benno, Martin - FAQ: Dani)

Test the new text style which is used for 'Errors', 'Warnings' and 'Spelling Errors'. There should be no big difference except on the Mac. Verify that both, 'Squiggly Line' and 'Native Problem Underline' look good.

Content assist: insert common prefix (Markus, Benno - FAQ: Dani)

Test that it works as expected but especially:

test that common prefix with exact case is inserted
test that common prefix with identical non-exact case is inserted and prefix updated
test that no proposal is inserted if there are other choices (e.g. SWT.NON<code assist>) - this was broken in earlier releases

Content assist: template proposal availability and relevance (Martin, Benno - FAQ: Dani)

Test that it works as expected but especially:

test that template proposals always appear when the prefix matches
test that Java keywords appear before templates, e.g. in if (o ins<code assist>)

Improved key binding support for content assist and quick fix (Martin, Benno - FAQ: Dani)

This affects completion proposal popup navigation while still in the editor.

test that Up/Down works
test that Home/End works
test that PageUp/PageDown works
test that Ctrl+P and Ctrl+N work when in Emacs mode

Javadoc view shows constant value (Benno, Martin - FAQ: Dani)

test that the description shows the constant value where possible
test that the hex value is correct
test with fields that aren't open in an editor (e.g. select in Package Explorer)

Runnable Jar Export wizard (Markus, Dani - FAQ: Benno)

test that all java application launch configurations are available
test that exported jars are executable
test with different libraries, set of libraries
test usability

Fine grained search UI (Dani, Markus - FAQ: Martin)

test UI in search dialog
test result view

Extract method participants (Markus, Benno - FAQ: Martin)

write a example

Text search matches (Dani, Markus - FAQ: Martin)

matches on long lines

Find occurrence improvements (Dani, Markus - FAQ: Martin)

link with editor
quick menu is now context sensitive

Quick fixes (Benno, Dani - FAQ: Martin)

create getter/setter for unused field
remove unused SuppressWarning

org.eclipse.jface.text.source.IAnnotationModelExtension2 (Markus, Dani - FAQ: Benno)

test the new API
Javadoc correct
is the implementation correct
is it useful

Exception variable name template resolver (Martin, Dani - FAQ: Dani)

test that the 'try' and the 'catch' templates use the exception name from the code style preference page
test that the 'try' and the 'catch' templates use the exception name from the code style project properties when configured
in the 'Edit Template' dialog test that content assist shows the new variable and that F1 help contains it

Bug Verification

Every tester has to verify 0.25 bugs ;-). Before starting to verify a bug add a comment indicating that you are about to verify it.