| <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| <html><head> |
| |
| <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>3.3 M5 Test Plan</title> |
| |
| <style type="text/css"> |
| h4 { margin-bottom: .5em; margin-top: 1.5em } |
| ul { margin-top: .5em } |
| ul li ul { margin-top: 0em; margin-bottom: .25em } |
| </style></head> |
| <body> |
| <h1>3.3 M5 Test Plan</h1> |
| Test day: Tuesday, 2007-2-6<br> |
| Test Build: I20070206-0010<br> |
| Components: Platform Search, Platform Text, JDT Text and JDT UI<br> |
| Testers: Benno, Dani, Markus<br> |
| |
| <h2>Goal</h2> |
| <ul> |
| <li>test new functionality added since 3.3 M4</li> |
| <li>verify that severe bugs are correctly fixed</li> |
| <li>sanity check performance</li> |
| </ul> |
| |
| |
| <h2>Test New Functionality </h2> |
| <em>First test all those items where you are listed as first tester.</em> |
| |
| |
| <span style="font-weight: bold;"><br> |
| <br> |
| Deprecated and read-only classpath variables (Benno, Dani - FAQ: Markus)</span><br> |
| <ul> |
| <li>check Java Build Path properties page</li> |
| <li>check the quick fix in the Problems view to configure build path for build path problems</li> |
| <li>create a JUnit project with Eclipse 3.1 and then check the Quick Fix 'Use the JUnit 3 library'</li> |
| </ul> |
| <span style="font-weight: bold;">Rename refactoring in Java editor (Dani, Benno - FAQ: Markus)</span><br> |
| <ul> |
| <li>test moving around and minimize/restore popup</li> |
| <li>test keyboard interaction and popup links</li> |
| <li>check that links are disabled if new name is invalid</li> |
| </ul> |
| <span style="font-weight: bold;">Per Project Settings for Save Actions </span><span style="font-weight: bold;"> (Dani, Markus - FAQ: Benno)</span> |
| <ul> |
| <li>check that the new property and preference page is easier to use than in M4<br> |
| </li> |
| <li>test that project settings are used if project does have project settings and that workspace settings are used otherwise</li> |
| <li>check that settings can be shared through source control system |
| and that accepting incoming settings does change the save action |
| project setting</li> |
| </ul> |
| <span style="font-weight: bold;">New Clean Ups</span><span style="font-weight: bold;"> </span><span style="font-weight: bold;"> (Markus, Dani - FAQ: Benno)</span> |
| <ul> |
| <li>test remove trailing whitespace (all and ignore empty). Check that result is as expected</li> |
| <li>test sort members clean up (all members and exclusive fields, enums, initializers). Check that result is as expected</li> |
| <li>test both clean ups also on save</li> |
| </ul> |
| <span style="font-weight: bold;">Format by Comment Type </span><span style="font-weight: bold;"> </span><span style="font-weight: bold;"> (Dani, Markus - FAQ: Benno)</span> |
| <ul> |
| <li>test new UI on formatter modify dialog, tab page 'Comments'</li> |
| <li>check that changing the settings on the page has the expected effect when formating source code</li> |
| </ul> |
| <span style="font-weight: normal;"></span><span style="font-weight: bold;">Open Type Dialog (Dani, Benno - FAQ: Markus)<br> |
| </span>This is the old code.<br> |
| <ul> |
| <li>test that it works as in M4.</li> |
| </ul> |
| <span style="font-weight: bold;">New Type Selection Dialog</span><span style="font-weight: bold;"> (Dani, Benno - FAQ: Markus)</span><br> |
| This is the new code. Can be tested e.g. in the New Class wizard.<span style="font-weight: normal;"></span> |
| <ul> |
| <li><span style="font-weight: normal;">test functionality</span></li> |
| <li><span style="font-weight: normal;">compare with M4</span></li> |
| </ul> |
| <span style="font-weight: bold;"> JUnit Launching (Markus, Dani)</span><br style="font-weight: normal;"> |
| <ul> |
| <li><span style="font-weight: normal;">test normal JUnit launcher and PDE JUnit launcher</span></li> |
| <li><span style="font-weight: normal;">test that developing a 3.1 and 3.2 application is no problem</span></li> |
| <li><span style="font-weight: normal;">run with older launch configurations to verify that they still run</span></li> |
| </ul> |
| <span style="font-weight: bold;">Package Explorer</span><span style="font-weight: bold;"> (Benno, Markus)</span> |
| <ul> |
| <li><span style="font-weight: normal;">double click on a closed project to open a project</span></li> |
| <li><span style="font-weight: normal;">working set mode: revealing elements in collapsed working sets</span></li> |
| </ul> |
| <span style="font-weight: bold;">Getter Setter Dialog </span><span style="font-weight: bold;"> (Markus, Dani)</span> |
| <ul> |
| <li><span style="font-weight: normal;">test new option to remove final modifier when creating a setter</span></li> |
| </ul> |
| <span style="font-weight: bold;">Extension-Point for Hyperlink Detectors</span><span style="font-weight: bold;"> (Markus, Benno - FAQ: Dani)</span> |
| <ul> |
| <li>verify that the extension point doc is accurate</li> |
| <li>verify that you can create your own detector (e.g. one for "bug nr" -» opens bug in bugzilla)<br> |
| </li> |
| <li>test the preference page</li> |
| </ul> |
| <span style="font-weight: bold;">Text Drag & Drop (Benno, Markus - FAQ: Dani)<br> |
| </span> |
| <ul> |
| <li><span style="font-weight: normal;">verify functionality</span></li> |
| <li><span style="font-weight: normal;">verify preference to enable/disable the feature</span></li> |
| </ul> |
| <span style="font-weight: bold;">Improved Code Assist For Static Imports (Markus, Benno - FAQ: Dani)</span> |
| <ul> |
| <li>test the new functionality (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=167387">167387</a> |
| <span style="display: none;"></span> |
| |
| |
| for details)</li> |
| </ul> |
| <span style="font-weight: bold;">Check Prompting When Closing Dirty Editors Opened in Different Editors</span><span style="font-weight: bold;"> (Benno, Markus - FAQ: Dani)</span><br> |
| Java, Text and compare editors now not only share their model while |
| typing but can also be treated the same when closing. The user will be |
| asked to choose whether to use the new or the old behavior.<br> |
| <ul> |
| <li>test that the user gets asked<br> |
| </li> |
| <li>test old behavior mixing different kinds of editors<br> |
| </li> |
| <li>test new behavior mixing different kinds of editors (only last editor asks to save)</li> |
| </ul> |
| <h2>Bug Verification</h2> |
| <em>There are 16 bugs meaning that everyone has to verify 5-6 bugs. Before starting to verify a bug add a comment indicating |
| that you are about to verify it.</em> |
| <ul> |
| <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&product=JDT&component=UI&priority=P1&priority=P2&target_milestone=3.3%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id"> |
| JDT UI bugs P1/P2, 3.3 M5</a></li> |
| |
| <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&priority=P1&priority=P2&target_milestone=3.3%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id"> |
| Platform Text and Search bugs P1/P2, 3.3 M5</a></li> |
| |
| <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&product=JDT&component=UI&bug_severity=blocker&bug_severity=critical&bug_severity=major&target_milestone=3.3%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id"> |
| JDT UI bugs blocker/critical/major, 3.3 M5</a></li> |
| |
| <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&bug_severity=blocker&bug_severity=critical&bug_severity=major&target_milestone=3.3%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id"> |
| Platform Text and Search bugs blocker/critical/major, 3.3 M5</a></li> |
| </ul> |
| |
| </body></html> |
