3.2 Two Day Test Pass: JDT UI, JDT Text, Platform Compare, Platform Text, and Platform Search

Testers: Benno, Dani, Johannes, Markus, Tobias, Tom

Goal: Find stop-ship bugs

overall testing of the build
test new 3.2 functionality
test Java 5.0 functionality:
whenever you create some test code please use 5.0 language features whenever possible. For example add a type parameter to every new class.
test corner cases
test setups which we typically don't use during development (for example no Plug-in development)
keep an eye on handling of error situations
- watch log
- error messages

Setup / Introduction

Build

Always use latest available Eclipse-SDK 3.2 RC2 candidate (currently I20060428-0010)

Platforms

Linux-GTK FedoraCore (Tom)
Mac OS X (Markus ½ day)
Windows XP (all but Tom)

General Items (everybody)

whenever you have to fill in data in dialogs try to fool the dialog by providing incomplete or bogus input
watch for view updating (Package Explorer, Java Browsing perspective, Java Outline page) when source content gets changed

use of different fonts (everybody)

change font for text editor and dialogs to different font
check that dialogs are rendered correctly
- specified dialog font is used
- no buttons and labels clipped

Test Multiple Monitor setup (Markus)

detached views
dialogs pop up on correct monitor

Workspace Setup

Setup workspace in a way unusual compared to your normal setup. Testing should take place in one of the following workspace setups. When setting up the workspace test also the functionality to setup this workspace style:

use external projects (Benno)
use linked resources (Tobias)
- linked output folders
- linked source folders
- linked and nested source folders
- test rendering in views
- linked class folders
use multiple output folder (Dani)
use combination of exclusion & inclusion filters (Markus)
use user defined library containers (JUnit as a user defined library) (Tom)
- quick fixes for unbound user libraries
- quick fixes for build path problems
full source workspace (Tobias)

Java Editor in Single Method mode (Markus, Tobias, Tom)

half of the team should test with editor in single edit mode
corner case
- segmented mode, formatting, undo/redo

Multiple Windows (Benno, Dani, Johannes)

half of the team tests with multiple windows.
switch between windows for different actions
watch for wrong window popping to front
watch for wrong dialog parenting

Multiple Editor Areas (Tom, Markus)

test with multiple editor areas, i.e. multiple editor tab folders
watch for focus problems
watch for positioning problems when opening dialogs and info pops

Java Perspective / Browsing Perspective / Working Set mode

third of the team tests in browsing perspective (Dani, Johannes)
third of the team tests in Java perspective using project mode in package explorer (Tobias, Benno)
third of the team tests in Java perspective using the working set mode in the package explorer (Tom, Markus)

Automatic workspace refresh (Benno, Tobias)

half of the team tests with automatic workspace refresh enabled (Preferences > Workbench > Refresh workspace automatically

New 3.2 Functionality (except JUnit4) (Johannes, Benno)

Test all new features that have been added during 3.2 development. Start by testing the features mentioned in the New and Noteworthy documents and the milestone test plans (M1, M2, M3, M4, M5, M6).
Special items to test:

Extract Superclass refactoring:
- verify that the refactoring works as expected
- verify that navigation within wizard causes no problems
Refactoring Scripting:
Verify that refactorings which produce errors (refactoring stati and unexpected exceptions) are handled gracefully by the scripting framework

JUnit4 Support (Dani, Tobias)

Test the new JUnit4 integrations and verify that this doesn't break the previous JUnit3 support.

J2SE 5.0 (Tom)

Note, when testing Java 5.0 feature don't forget to test parameterized types that are subclasses of generic types as well as methods that use type parameters and varargs. For example MyList extends ArrayList<String> or <X. void foo(X x, String...).
See also the detailed 5.0 test plan.

General items (Markus, Tobias, Dani)

Accessibility Testing (Markus)

verify mnemonics in wizards/dialogs/menus
initial focus in dialogs
combination of color, form, and text.
status line information

Operations and Locked Workspace (Markus)

To lock the workspace use the org.eclipse.ui.examples.job plug-in from the Eclipse repository
Test Edit, Source and Refactoring actions when the workspace is locked
Test modifying project properties (build path, compiler settings, ...) when workspace is locked
You should always get the blocking dialog
Cancel the user action. Make sure that no OperationCancelException or other exceptions appear in the log

Actions (Markus)

Test all our actions from context and main menu.

enablement

verify that they don't fail

Preference Pages (Dani)

Test all our preferences.

Validate-Edit (Dani)

Check-out code from the repository in CVS Watch/Edit mode (stores file in read-only mode)
Test Editing, Source and Refactoring actions on files that are read-only
Expected result: actions should complete without errors

Compilation Units not on Build Path (Tobias)

Test Edit, Source and Refactoring actions for compilation units not on the build path.
Test for:
- editors opened on repository files
- editors opened on Java file excluded from the build path
- editors opened on Java files stored in Simple projects
Actions should either operate without an error, not be present or present a dialog that the CU is not on the build path

Workspace compatibility (Tobias)

Verify that an existing workspace can be started on the new version and is fully functional. Check the .log for serious problems.

upgrade a 3.1 workspace to 3.2
upgrade a 3.0 workspace to 3.2