3.1.1 Test Grid 1

Test day: Friday, September 2, 2005
Test Build: M20050831-1200 + the two plug-ins in \\Rosenberg.zurich.ibm.com\public\t\jabiru\plugin-export\M20050831-1200.from20050902_1247
Components: JDT/Text, JDT/UI, Platform/Search, and Platform/Text
Testers: Benno Baumgartner, Dirk Bäumer, Tom Eicher, Markus Keller, Daniel Megert, Tobias Widmer

3.1.1 Bug verification (all)

Carefully verify all bugs that got fixed in the 3.1.1 maintenance stream by not only using the listed scenario but also try to break the fix with variants of the listed steps.

Test method overriding - Tester: Tom Eicher (FAQ: Markus Keller)

create non-trivial cases of (non-)overriding methods and check that the override indicator annotation in the editor is correct, e.g.

methods whose signatures are different because the subtype is raw
overriding methods in parameterized anonymous types - verify that generated methods are correctly parameterized
type variables got renamed/added/removed or have different bound
methods that only differ in type arguments of a parameter
etc.

check that Source > Override/Implement methods behave reasonable in cases where an overriding method exists/does not exist

Code Assist - Tester: Markus Keller, Tobias Widmer (FAQ: Tom Eicher, Daniel Megert)

test code completion for static imports
try different combinations of incremental completion
test code assist inside Javadoc
test overriding methods in parameterized anonymous types - verify that generated methods are correctly parameterized
write the following statement by typing everything in (don't use code assist, but wait at every period for the auto-activated assist). Make sure that the auto-activated content assist does not interfere with your typing: new StringBuffer(new String("foobar").substring(1, 3).hashCode()).append(System.out).toString();

Generate Constructors Using Fields - Tester: Dirk Bäumer (FAQ: Tobias Widmer)

verify that reasonable parameter and variable names are generated

Open Type Dialog - Tester: Daniel Megert (FAQ: Dirk Bäumer)

Remove types from the workspace which are part of the open type dialog's history. Make sure that when reopening the dialog the types don't show up in the history any more. Remove types by deleting types, change classpaths (remove a library), deleting containers (packages, source folders, ...), etc.

JUnit - Tester: Benno Baumgartner (FAQ: Dirk Bäumer)

Test executing all tests from a package, source folder. Make sure that the performance collecting all test cases (time between triggering the launch and the actual launch starts) is acceptable (less than a minute) for large containers and that all tests are executed.