3.3 M5 Test Plan

Test day: Tuesday, 2007-2-6
Test Build: I20070206-0010
Components: Platform Search, Platform Text, JDT Text and JDT UI
Testers: Benno, Dani, Markus

Goal

test new functionality added since 3.3 M4
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.

Deprecated and read-only classpath variables (Benno, Dani - FAQ: Markus)

check Java Build Path properties page
check the quick fix in the Problems view to configure build path for build path problems
create a JUnit project with Eclipse 3.1 and then check the Quick Fix 'Use the JUnit 3 library'

Rename refactoring in Java editor (Dani, Benno - FAQ: Markus)

test moving around and minimize/restore popup
test keyboard interaction and popup links
check that links are disabled if new name is invalid

Per Project Settings for Save Actions (Dani, Markus - FAQ: Benno)

check that the new property and preference page is easier to use than in M4
test that project settings are used if project does have project settings and that workspace settings are used otherwise
check that settings can be shared through source control system and that accepting incoming settings does change the save action project setting

New Clean Ups (Markus, Dani - FAQ: Benno)

test remove trailing whitespace (all and ignore empty). Check that result is as expected
test sort members clean up (all members and exclusive fields, enums, initializers). Check that result is as expected
test both clean ups also on save

Format by Comment Type (Dani, Markus - FAQ: Benno)

test new UI on formatter modify dialog, tab page 'Comments'
check that changing the settings on the page has the expected effect when formating source code

Open Type Dialog (Dani, Benno - FAQ: Markus)
This is the old code.

test that it works as in M4.

New Type Selection Dialog (Dani, Benno - FAQ: Markus)
This is the new code. Can be tested e.g. in the New Class wizard.

test functionality
compare with M4

JUnit Launching (Markus, Dani)

test normal JUnit launcher and PDE JUnit launcher
test that developing a 3.1 and 3.2 application is no problem
run with older launch configurations to verify that they still run

Package Explorer (Benno, Markus)

double click on a closed project to open a project
working set mode: revealing elements in collapsed working sets

Getter Setter Dialog (Markus, Dani)

test new option to remove final modifier when creating a setter

Extension-Point for Hyperlink Detectors (Markus, Benno - FAQ: Dani)

verify that the extension point doc is accurate
verify that you can create your own detector (e.g. one for "bug nr" -» opens bug in bugzilla)
test the preference page

Text Drag & Drop (Benno, Markus - FAQ: Dani)

verify functionality
verify preference to enable/disable the feature

Improved Code Assist For Static Imports (Markus, Benno - FAQ: Dani)

test the new functionality (see bug 167387 for details)

Check Prompting When Closing Dirty Editors Opened in Different Editors (Benno, Markus - FAQ: Dani)
Java, Text and compare editors now not only share their model while typing but can also be treated the same when closing. The user will be asked to choose whether to use the new or the old behavior.

test that the user gets asked
test old behavior mixing different kinds of editors
test new behavior mixing different kinds of editors (only last editor asks to save)

Bug Verification

There are 16 bugs meaning that everyone has to verify 5-6 bugs. Before starting to verify a bug add a comment indicating that you are about to verify it.