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

Testing days: Monday, 2010-05-24 (public holiday in Switzerland) and Tuesday 2010-05-25
Test Build: I20100520-1744 (or declared RC2 build)
Testers: Dani, Deepak, Markus and Raksha

Platforms

Linux GTK: Dani
Mac OS X: Markus
Windows XP: Deepak, Raksha
Windows 7: - Dani
Windows Vista: -

Workbench Setup

Use the Java editor breadcrumb whenever possible.

Dani tests using the Java browsing perspective
Deepak tests using the Java perspective with Package Explorer replaced by the Project Explorer
Markus tests using the Java perspective with Package Explorer in working set mode
Raksha tests using the Java perspective with Package Explorer in project mode

Make sure all RC* Fixes are verified (Deepak, Markus)

First thing is to make sure that all RC1 and RC2 fixes are verified.

New 3.6 Functionality (Deepak, Dani)

Test all new features that have been added during 3.6 development. This can be done by testing the features mentioned in the M1-M7 New and Noteworthy documents.

Views and Editors (Dani, Raksha)

resize behavior
scrolling (rulers)
different fonts and colors
detached views
multiple windows
multiple editor areas
help support

Compilation Units not on Build Path (Deepak, Raksha)

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 Setup (Markus, Deepak)

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
use linked resources
- linked output folders
- linked source folders
- linked and nested source folders
- test rendering in views
- linked class folders
use multiple output folders
use combination of exclusion & inclusion filters
use user defined library containers (JUnit as a user defined library)
- quick fixes for unbound user libraries
- quick fixes for build path problems
full source workspace

Workspace compatibility (Raksha, Markus)

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.4 workspace to 3.6
upgrade a 3.5 workspace to 3.6

Freestyle Testing (all)

Once all of the above test items are done (including those where you are listed as second tester), start with a fresh workspace and change the settings in a way you normally don't work.

Implement a little feature or tool or fix one of your favorite bugs.