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

Testers: Benno, Dani, Markus, Martin, Karsten

Build

Platforms

• Linux-GTK (Dani 1/2 day)
• Mac OS X (Markus 1 day)
• Windows Vista (Martin)
• Windows XP (all others)

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
• dialog layout
• Help
  

Views and Editors (Dani)

• resize behavior
• test for unnecessary flickering
• different fonts and colors
• detached views
• multiple windows
• multiple editor areas
• watch for focus problems
• help support
  

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

Java Perspective / Browsing Perspective / Working Set mode

• third of the team tests in browsing perspective (Dani)
  
• third of the team tests in Java perspective using project mode in package explorer (Karsten, Benno)
  
• third of the team tests in Java perspective using the working set mode in the package explorer (Martin, Markus)
  

Actions (Karsten)

• 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 (Dani)

• 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 (Dani)

• upgrade a 3.1 workspace to 3.3
• upgrade a 3.2 workspace to 3.3

New 3.3 Functionality (Benno)

• Actions on Save
• try unusual settings
• try on code with compile errors
• undo
  
• Lightweight refactoring:
• undo
• progress reporting
• change options in dialog (find textual references)