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



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:

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

Use the 'Annotations' preference page to test that:

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:

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

Test that it works as expected but especially:

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.

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

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

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

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

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

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

Quick fixes (Benno, Dani - FAQ: Martin)

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

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

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.