3.4 Two Day Test Pass: JDT UI, JDT Text, Platform Text,
and Platform Search
Testers: Benno, Dani, Markus, Martin
Build
Eclipse-SDK 3.4 RC1
Platforms
- Linux-GTK (Martin)
- Mac OS X (Markus)
- Windows Vista (Benno)
- Windows XP (Dani)
Workbench Setup
Use the Java editor breadcrumb whenever possible.
- Dani tests using the Java browsing perspective (Dani)
- Benno tests using the Java perspective with Package Explorer in project mode
- Martin tests using the Java perspective with Package Explorer in working set mode
Verify RC1 Fixes (all)
First thing is to verify all our RC1 fixes.
Every tester has to verify 20 bugs. Before starting to verify a bug add a comment indicating
that you are about to verify it.
New 3.4 Functionality (Dani)
Test new features that have been added during 3.4 development.
Start by testing the features mentioned in the New and Noteworthy
documents.
Dialogs, Preferences and Wizards (Martin)
- input validation
- whenever you have to fill in data in dialogs try to fool the
dialog by providing incomplete or bogus input
- different fonts and colors
- test that fonts are applied on apply
- specified dialog font is used
- no buttons and labels clipped
- mnemonics
- test that mnemonics are defined
- test for conflicts - major items should have a unique mnemonic
- initial focus in dialogs
- size and position
- all input dialogs should be resizable
- dialog size should be remembered
- dialog position only for special dialogs
- test multiple monitors
- NLS problems: modify our NLS files with bogus content
- Help
Views and Editors (Dani)
- resize behavior
- different fonts and colors
- detached views
- multiple windows
- multiple editor areas
- help support
Actions (Benno)
- enablement
- verify that they don't fail
- locking
- 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
- validate edit
- 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 (Martin)
- 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)
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)
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.2 workspace to 3.4
- upgrade a 3.3 workspace to 3.4
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.