3.5 Two Day Test Pass: JDT UI, JDT Text, Platform Text and Platform Search
Test day: Friday, 2009-05-15 and Monday 2009-05-18
Test Build: I20090514-2000 and I20090515-1143
Testers: Markus, Raksha, Pawel and Dani
Platforms
Workbench Setup
Use the Java editor breadcrumb whenever possible.
- Dani tests using the Java browsing perspective
- Raksha tests using the Java perspective with Package Explorer in project mode
- Markus tests using the Java perspective with Package Explorer in working set mode
Verify RC1 Fixes (Markus, Dani)
First thing is to verify all our RC1 fixes.
Every tester has to verify 18 bugs. Markus takes the bugs with lower numbers
New 3.5 Functionality (Raksha, Dani)
Test new features that have been added during 3.5 development.
Start by testing the features mentioned in the M1-M7 New and Noteworthy
documents.
Views and Editors (Raksha, Dani)
- resize behavior
- different fonts and colors
- detached views
- multiple windows
- multiple editor areas
- help support
Compilation Units not on Build Path (Dani, Markus)
- 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
Java Compare (Raksha, Markus)
- verify that comparing difference versions works
- verify that compare with each other works
- verify that the structure is update while typing
- verify that Java editor features like Ctrl+O, F3 and content assist work
Workspace Setup (Markus, Dani, Pawel)
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 folder
- 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 (Markus, Raksha)
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.3 workspace to 3.5
- upgrade a 3.4 workspace to 3.5
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 fix one of your favorite bugs.