3.6 M4 Test Plan

Test day: Tuesday, 2009-12-08
Test Build: I20091208-0100 or newest available
Components: Platform Search, Platform Text, JDT Text and JDT UI
Testers: Deepak, Markus, Raksha, Tom

Platforms

Windows XP: Raksha, Deepak
Windows Vista 64: Tom
Windows 7: -
Linux-GTK: -
Mac OS X: Markus

Goal

test new functionality added since 3.6 M3
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.

Content Assist: Better handling of getter/setter proposals (Deepak, Raksha - Questions: Markus)

test that setter proposals for non-final fields appear and work (bug 51187)
test that setter proposals do not appear for final fields (bug 51187)
test all expected proposals appear in case of name clashes (bug 285568)

Open Attached Javadoc using preferred browser (Deepak, Tom - Questions: Markus)

Test that opening attached Javadoc (formerly Open External Javadoc) works as expected (bug 251789).

test that it works in the editor using the menu and the shortcut
test that it works in the hover via button which is in the hover
test that it works in the Javadoc view via shortcut and via local toolbar button
test that it works when a web page is shown in the Javadoc view (bug 295905).

Textual editors ignore orientation switching (Tom, Deepak - Questions: Markus)

Note: Test in a normal Text widget that this feature is enabled at all (you may have to install an RTL keyboard language like Farsi).

test that Ctrl + left_Shift and Ctrl + right_Shift don't switch widget orientation bug 291950

Search dialog no longer clipping UI elements (Markus, Deepak - Questions: Markus)

test in all search pages that no UI elements get clipped when using large fonts bug 293661

Virtual Folders AKA Groups (Markus, Deepak - Questions: Szymon)

overall testing with focus on JDT

Resource tree filtering (Raksha, Markus - Questions: Szymon)

overall testing with focus on JDT

Background computing of Type Hierarchy (Deepak, Markus - Questions: Raksha)

Test that the type hierarchy computation happens in the background (bug 30881)

test for both restore and refresh on new input
test that the viewer is empty till the new hierarchy is updated, and grey when there's no input
test for long running computations and all 3 types of hierarchy computations
test that opening a new hierarchy cancels previous computation

Support for multi-fixes in Problem Hover (Deepak, Markus - Questions: Raksha)

Test that multi-fixes are supported in the problem hover (bug 296318)

test that the similar problems are correctly identified and the fix is applied to all similar problems in the file
test that multi-fix link is not shown when only one problem is present in the file
test that the link is properly indented along with the icon

Open Implementation hyperlink (Deepak, Markus - Questions: Raksha)

sanity-check that it behaves as expected (jump to single implementation / open quick hierarchy for multiple)

Call Hierarchy: New "Expand with Constructors" dialog (Deepak, Markus - Questions: Raksha)

test that method and type preferences work
test that preferences that have been stored in a 3.5 workspace are properly converted when the 3.5 workspace is started with the test build

Preference UI Changes (Markus, Raksha - Questions: Deepak)

verify the note on Compiler > Javadoc preference page - 'Note: This also affects features like search, refactoring, content assist and missing/unused imports.' (bug 292860)

NLS Tooling (Raksha, Markus - Questions: Deepak)

verify that Find Broken Externalized Strings utility can handle constants for message keys (bug 247012)

Externalized Strings (Raksha, Deepak - Questions: Deepak)

verify that "(s)" is not used as placeholder for singular and plural (bug 266094)
verify that there are no unused externalized strings in JDT UI (bug 294552)

JUnit 4 (Tom, Deepak - Questions: Markus)

The org.junit 3.8.2 plugin stayed and an org.junit 4.7.0 has been added, see http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes:

verify that the JUnit library works for JUnit 3 and JUnit 4 (add library to build path, verify that source is attached and that tests can be executed)
verify that Plug-in tests work when a plug-in:
- requires org.junit;bundle-version="[3.8.2,3.9.0)" and uses Execution Environment (EE) 1.4
- requires org.junit;bundle-version="3.8.2" and EE 1.4 or 1.5
- requires org.junit;bundle-version="4.7.0" and EE 1.5
- requires org.junit4;bundle-version="4.3.1" and EE 1.5

JUnit launch configuration dialog (Raksha, Deepak - Questions: Markus)

On the "Test" tab of "JUnit" and "JUnit Plug-in Test" launch configurations, the "Test Method" is now editable

verify that adding / removing a test method works
verify that the Search button finds the test methods
test with JUnit 3 and JUnit 4 tests (hint: the selected test runner influences the found test methods

JUnit View: Rerun Failed First also for JUnit 4 (Raksha, Deepak - Questions: Markus)

verify that the "Rerun Test - Failed First" action in the JUnit view toolbar is also active for JUnit 4 tests
verify that it really runs failed tests first

Source actions generate methods in declaration order (Raksha, Deepak - Questions: Markus)

See Bug 140971.

verify that order of generated methods is the same as the order of the original elements

Test 3.5.2 Fixes

Make sure to verify all Platform Search, Platform/JDT Text and JDT UI fixes.

Test all fixes against 3.5.2 (Deepak)

Use M20091202-0800.

Test all fixes against 3.6 M4 (Markus)

Bug Verification (All)

Before starting to verify a bug add a comment indicating that you are about to verify it.