3.2 M3 Test Grid for JDT/UI and Text Components

Test day: Tuesday, November 1, 2005
Components: JDT/Text, JDT/UI, Platform/Search and Platform/Text
Testers: Dirk Baeumer, Benno Baumgartner, Tom Eicher, Markus Keller, Tobias Widmer, Philip Mayer

Bug verification (all):

• Verify all bugs fixed during the M3 cycle

 

• Start with P1 and P2 bugs:

·         P1 & P2 bugs in JDT/UI & JDT/Text

·         P1 & P2 bugs in Platform/Search & Platform/Text

Open Type dialog (Tobias, Markus):

• History consistency check now takes place in background
• ensure that deleted types don't show up in the dialog anymore
• quickly open the dialog after deleting types which are referenced in the history. Ensure that you see a blocked dialog waiting for the background consistency check to finish.
• open the dialog directly after start-up (while the Initialize Java ... job is still running). Ensure that you see a blocking dialog.

 

• Pattern matching support is now used from JDT/Core:
• test that all patterns work correctly (camel case, wildcard, < and blank for end of string)

 

Package Explorer (Tom, Philip):

• The package explorer now supports non Java working sets when in working set mode. The only restriction is that the top level elements of the working set can be adapted to IProject.
• test that those working sets can be selected
• test that the actions (refresh, open/close, ...) on these working sets work correctly
• test that updating the projects (renaming, deleting, ...) updates the working sets referencing these projects

 

Eclipse File System (Markus, Tom):

• Jar Creation
• test Jar exporting. Ensure that jars are created correctly (not only table of contents). Try to run a program using such a Jar.
• rename and delete the projects for which a Jar got created.

 

• New Java Project wizard
• test creating a project on a existing location (delete a project, but don't delete its content and recreate it)
• ensure that a backup of the .classpath and .project file is created in the OS specific temp directory
• modify the classpath in the wizard and press cancel. Make sure that the content of the .classpath and .project file is correctly restored from the tmp directory

 

• Existence Tests:
• create a new project, source folder and type where a file on disk with the same name already exists but without having the resource in the workspace tree. Make sure that an error is displayed warning about the existence.

 

• Refreshing Workspace
• make sure that external project deletion is correctly discovered by the refresh action (create a project, delete it on disk and refresh it)

 

Clean Up Refactoring (Tom, Benno):

 

• Test cleanups by applying all sorts of cleanup combinations to different sets of compilation units.

 

New Java Project wizard (Benno, Dirk):

 

• On first page test selecting JDK. Check that the compiler compliance level and the JDK is set correctly after finishing the wizard.
• On second page test create new source folder action.

 

Project Build Path properties (Dirk, Tobias):

• On build patch properties page for Java project under source tab test link source action.

 

Sort Members action (Tobias, Markus):

• Test sort members action
• Test if it excludes fields, enum consts and initializers.

 

Javadoc Content Assist (Philip, Tom):

• Test javadoc content assist
• test normal assist within @see and {@link} tags
• test that only these tags show up that make sense (e.g. @param for methods and parameterized types)
• test type completion outside of any tag, completing the type name or the {@link reference)
• verify import behavior for type completion: normal import behavior inside tags, no imports for informal (<code>) references