Kepler Two Day Test Pass

Testing days: Monday, 2013-05-06 and Tuesday 2013-05-07
Test Build: Declared 4.3 M7/RC0 build
Testers: Manju, Noopur, Markus and Dani

Setup

Platforms

Linux GTK: Noopur
Mac OS X 10.8: Markus
Windows 7: Manju, Dani

Workbench Setup

Use the Java editor breadcrumb whenever possible.

Dani tests using the Java browsing perspective
Manju 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
Noopur tests using the Java perspective with Package Explorer in project mode

Each new bug must state whether it is a regression or not.

New Kepler Functionality (All)

Test all (not just JDT!) new features that have been added during Kepler development. This can be done by testing the features mentioned in the M1-M7 New and Noteworthy documents.

M1 & M2 (Dani)
M3 & M4 (Manju)
M5 & M6 (Markus)
M7 (Noopur)

Smoke test (Manju, Noopur)

Peform the {JDT/UI, Text, Search} Smoke Test. Note that the test script may be a bit out of date, since we don't run this regularly any more.

Manju: Part 1
Noopur: Part 2

Views and Editors (Noopur)

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

Workspace and Project Setup (Markus)

Setup workspaces and projects in ways unusual compared to your normal setup. Test the following workspace and project setups:

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 resource filters
use multiple output folders
use source folders with ignored compile problems
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 (Manju)

Verify that an existing workspace can be started on the new version and is fully functional. Also verify that preferences exported with an older workspace can be imported and work. Check the .log for serious problems.

upgrade a 3.7 workspace to 4.3
upgrade a 3.8 workspace to 4.3
upgrade a 4.2 workspace to 4.3

Verify that projects created and checked into a repository with an older version can be checked out with Kepler.

About Info (Dani)

Verify that all plug-ins and features appear correctly in the About dialog:

bundles are signed
copyright notices are up-to-date
plug-in and feature versions are correct
all features and plug-ins have a license agreement

Freestyle Testing (All)

Once all of the above test items are done, start with a fresh workspace and change the settings in a way you normally don't work.

Implement a little feature or tool or create a patch for one of your favorite bugs. Use refactorings and UI gestures you don't normally use.