3.7 M6 Test Plan
Test day: Tuesday, 2011-03-08
Test Build: I20110307-2110
Components: Platform Search, Platform Text, JDT Text and JDT UI
Testers: Deepak, Markus, Rajesh and Raksha
Platforms
Goal
- test new functionality added since M5
- verify that severe bugs are correctly fixed
- sanity check performance
Test New Functionality
First test all those items where you are listed as first tester.
Undo in Java breakpoint condition editor (Deepak, Markus - Questions: Markus)
Verify that Undo and Redo work in the Java breakpoint editor.
- verify that it works in the Breakpoints view
- verify that it works in the Breakpoint properties dialog
Editor (input) as search scope (Raksha, Rajesh - Questions: Markus)
Verify that the editor (input) can be used as search scope in the search dialog.
- verify that 'Selected resources' is enabled when the search dialog is opened while an editor is active
- verify that it all search pages work
- verify that with Text, Java and PDE editors
API and UI to configure SCM URLs for import (Markus, Deepak - Questions: Ankur and Tomasz)
There are new APIs and a new extension point that allows to configure SCM URLs for import (bug 330490).
- verify that it works
- review the APIs and extension point
Correct number of parentheses (Rajesh, Markus - Questions: Deepak)
Try to find a case where extra parentheses are created or where necessary parentheses are removed/not added. Only known case is bug 337680.
- verify that 'Remove unnecessary parentheses' cleanup removes all unnecessary parentheses, but does not remove any necessary parentheses.
- verify that refactorings, quick assists, quick fixes do not create any extra parentheses.
Verify the new 'Put expression in parentheses' quick assist (Rajesh, Raksha - Questions: Deepak)
- verify that it works for all kinds of expressions, e.g cast, conditional etc
- make sure that 'parentheses' (plural) and 'parenthesis' (singular) are used correctly.
Quick assists (Raksha, Markus - Questions: Deepak)
- verify that 'Pull Negation up' and 'Push Negation down' quick assists always do something meaningful, e.g they are not available on cases like "if (!b) { }"
- verify that inversion of 'value' of conditional expressions is correct, e.g. in 'Invert if statement', 'Push Negation down', 'Pull Negation up', 'Invert local variable' etc
Inline refactoring (Markus, Raksha - Questions: Deepak)
- Inline method refactoring: verify that the returned value is cast if and only if required.
- Inline constant/temp refactoring: verify that the initializer is cast if and only if required.
- Test for cases involving generics and generics with wildcards.
NLS tooling (Rajesh, Raksha - Questions: Deepak)
- verify that the tooling (e.g. hovers for NLSed strings) does not throw an IAE when a properties file contains an invalid unicode escape. Only known case is bug 337086.
Hyperlink/Open Declaration on break and continue (Deepak, Rajesh - Questions: Raksha)
- verify that break and continue are now clickable with and without labels.
- verify that open action on break jumps to the end of target statement, while on continue it jumps to the beginning of the target statement and on labels it jumps to the label declaration.
- verify that hyperlink are enabled only when there's a valid target.
Ensure consistent relative ordering of active working sets (Deepak, Rajesh - Questions: Raksha)
- verify that WorkingSetDropAdapterTest.testRearrange* pass in any order the working sets are created or set as active.
- verify that WorkingSetDropAdapterTest.testRearrange* fails with IAE when setWorkingSets(..) with different order of all and active working sets as parameters (in PackageExplorerPart.internalTestShowWorkingSets(..))
Working set order lost for non visible working sets (Package Explorer) (Markus, Deepak - Questions: Raksha)
- verify that non visible working sets can be re-ordered through Configure Working Sets dialog
- verify that drag and drop for working sets works fine
- verify that restoring from memento keeps the order and restores all working sets when new working is added while closing Package Explorer
- verify that Working Sets Assignment and toggle sort work fine
Quick Fixes more relevant than Quick Assists (Raksha, Deepak - Questions: Markus)
We've fixed a few problems with Quick Assists whose priority was too high in case a warning or error
was present at the caret location (e.g. Rename in file, Extract to local variable), or where the
top proposal was not the most likely action (e.g. "Return the allocated Object" was hiding "Assign statement to local variable")
- sanity-check quick fix proposal ordering for various problem kinds
Quick Fixes for generics-related problems (Deepak, Rajesh - Questions: Markus)
- verify that quick fixes for generics-related problems make sense and have the right relevance
- check raw types, wrong type arguments, type mismatch in assignment, unchecked method invocation
Hyperlink/Open Declaration on {@inheritDoc} tags (Raksha, Rajesh - Questions: Markus)
- verify that links work and jump to the correct target
Content Assist on methods with 'Fill method arguments' preference enabled (Deepak, Raksha - Questions: Markus)
- verify that typing ',' jumps to the next argument
- verify that typing ';' behaves according to the setting for semicolons on the Typing preference page
- verify that typing in a linked field and then pressing 'Enter' behaves consistently no matter how quickly 'Enter' is pressed after typing the argument
Type Hierarchy: Method overriding problems (Rajesh, Deepak - Questions: Markus)
We've fixed problems in the Type Hierarchy where methods were wrongly found as overriding/overridden methods.
- verify that only instance methods are considered
- verify that private methods are not considered
- verify that constructors are not considered (even if a method has the same name as a constructor)
Indentation (Markus, Deepak - Questions: Rajesh)
- test indentation in Java Editor on Enter, Ctrl+I, and Format
- perform free-style tests, without looking at fixed bugs -- goal is to find unanticipated regressions
-
known bugs
Bug Verification (All)
Before starting to verify a bug add a comment indicating that you are about to verify it.