ui/r3_2/testpass/M5_Test_Plan.html - gerrit/www.eclipse.org/jdt - Git at Google

 <!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.2 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.2 M5 Test Grid</h1>
 Test day: Tuesday, 2006-02-14<br>
 Test Build: latest I-build<br>
 Components: JDT/Text, JDT/UI, Platform/Search, Platform/Compare and Platform/Text<br>
 Testers: Martin, Dani, Markus, Tobias, Benno, Tom<br>

 <h4>Goal</h4>
 <ul>
   <li>test new functionality added since M4</li>
   <li>sanity check performance</li>
   <li>verify that severe bugs are correctly fixed</li>
 </ul>

 <h4>Verification of Bugs (ALL)</h4>
 <span style="font-style: italic;">There are 246 so everyone should verify 41. Take high-priority bugs first.<br>
 Before starting to verify add a comment that you take a bug for verification.</span><br>
 <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.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
   JDT UI bugs P1/P2, 3.2M5</a></li>

 <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&component=Compare&priority=P1&priority=P2&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
   Text, Search, and Compare bugs P1/P2, 3.2 M5</a><p></p></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.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
   JDT UI bugs blocker/critical/major, 3.2 M5</a></li>

 <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&component=Compare&bug_severity=blocker&bug_severity=critical&bug_severity=major&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
   Text, Search, and Compare bugs blocker/critical/major, 3.2 M5</a><p></p></li>

 <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&product=JDT&component=UI&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
   all JDT UI bugs 3.2 M5</a></li>

 <li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&component=Compare&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
   all Text, Search, and Compare bugs 3.2 M5</a><p></p></li>

 </ul>

 <h4>Watch out for cheese and odd behavior in the Text and Java editors (ALL)</h4>
 <p></p>
 <hr/>

 <h4>New clean ups and new Clean Up Wizard UI (Markus, Tobias) (FAQ: Benno)</h4>
 <p>Check wording and test usability of new Clean Up Wizard</p>
 <p>Test new Clean ups:</p>
 <ul>
 <li>Add serial version Id (generated/default)</li>
   <li>Remove unnecessary blocks</li>
   <li>Remove unnecessary casts</li>
 </ul>

 <h4>Build path wizards (Martin, Tom) (FAQ: Benno)</h4>
 <p>Test new build path wizards:
 <ul>
 <li>Link source folder</li>
 <li>Add source folder</li>
 <li>Edit inclusion/exclusion patterns</li>
 </ul>
 By starting the wizards through:
 <ul>
 <li>New Project creation wizard</li>
 <li>Package explorer context menu</li>
 <li>Projects build path properties</li>
 </ul>
 <ul>
 <li>Verify that there is no way to commit an invalide class path</li>
 <li>Check wording</li>
 <li>Test usability</li>
 <li>Test that renaming/removing/adding a source folder works as expected (i.e. that the corresponding files are removed/renamed/added as well)
 </ul>

 <h4>Type selection history (Tom, Markus) (FAQ: Benno)</h4>
 <p>Import types with:</p>
 <ul>
 <li>Code assist</li>
 <li>Organize import</li>
 <li>Add imports</li>
 </ul>
 <p>Verify that:</p>
 <ul>
 <li>Previous selected types are on top of the list if conflicting types</li>
 <li>Selection history is stored between sessions</li>
 </ul>
 <p>Try to find dialogs where it would also make sense to have the same history</p>

 <h4>Package Explorer 1 (Dani, Benno) (FAQ: Dirk)</h4>

 <ul>
 <li>test in workset mode</li>
 <li>create a couple of working sets having the same elements</li>
 <li>structurally change the content of the elements in the working set
  by adding, removing or moving elements.</li>
 </ul>

 <p>Ensure that:</p>
 <ul>
 <li>no elements get lost or rendered more often than they should</li>
 <li>they are rendered under the correct parent</li>
 <li>the selection is kept stable during these changes</li>
 </ul>

 <h4>Package Explorer 2 (Dani, Martin) (FAQ: Benno)</h4>
 <p>Make sure that compilation units are never parsed while exploring the package explorer/resource navigator/java browsing perspective (unless of course the cu needs to be parsed because the cu is expaned)</p>
 <ul>
 <li>Take a large cu (3MB+) watch out for ui freezes</li>
 <li>Test in flat and hierarchical mode</li>
 <li>Open context menu on elements</li>
 </ul>
 <p>See also bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=127105">127105</a></p>

 <h4>Editors (Tobias, Markus) (FAQ: Dani)</h4>
 <ul>
 <li>test Quick Fix in the Properties editor  (via menu and via key binding)</li>
 <li>test whether Quick Fix works in the Properties editor (via menu and via key binding)</li>
 <li>test whether Quick Fix works in the Java editor (via menu and via key binding)</li>
 <li>compare two *.properties files - verify that the compare editor opens</li>
 <li>compare two *.java files - verify that the compare editor opens</li>
 <li>test 1 1/2 click in the text and Java editor<br>
 	<ul>note: selection is done character by character and not word by word</ul></li>
 </ul>

 <h4>Read only status (Benno, Martin) (FAQ: Dani)</h4>
 <p>verify that the read-only status is correctly shown for:</p>
 <ul>
 <li>read-only *.java files</li>
 <li>*.class files</li>
 <li>types from a JAR</li>
 </ul>

 <h4>Generate hashCode() and equals() (Benno, Tom) (FAQ: Tobias)</h4>

 <ul>
 <li>Verify that correct code is generated</li>
 <li>Verify that warning messages appear in a dialog if either:
 	<ul>
    <li>the hashCode()/equals() is not implemented within the classhierarchy</li>
    <li>or the generated would reference a field whose type has
     unimplemented hashCode()/equals() methods.</li></ul></li>
 </ul>

 <h4>JAR Exporter (Markus, Martin) (FAQ: Tobias)</h4>

 <p>Test the export of JAR files with refactoring information</p>

 <p>Verify that the checked refactorings are indeed exported
 (refactorings.xml in the META-INF directory)</p>

 <h4>Replace JAR File (Dani, Tom) (FAQ: Tobias)</h4>
 <ul>
 <li>Test the replace of an existing JAR file on the build path with a new
 one containing refactoring information.</li>
 <li>Test replacing an existing JAR file which contains refactoring
 information with a new one containing the entire project history. The
 refactoring preview should only display the delta which has not yet been
 applied.</li>
 </ul>

 <h4>Refactoring Scripts (Dani, Benno) (FAQ: Tobias)</h4>
 <ul>
 <li>Test the creation and application of arbitrary scripts, containing
 several refactorings</li>
 <li>Verify that correct undos are generated</li>
 </ul>

 <h4>JUnit View History (Tobias, Benno) (FAQ: Markus)</h4>
 <ul>
 <li>test the view with concurrent JUnit Tests and JUnit Plug-in Tests</li>
 <li>test switching from/to running/stopped/finished test runs</li>
 <li>verify that progress is correctly reported in progress bar/counters</li>
 <li>check view icons (shows progress if view is invisible fast view; sensible image when view is visible)</li>
 </ul>

 <h4>Introduce Indirection (Tom, Dani) (FAQ: Markus)</h4>
 <ul>
 <li>test with methods from source and with binary methods (start at an invocation site)</li>
 <li>test with overridden methods</li>
 </ul>

 <h4>Problems view (Tom, Tobias) (FAQ: Martin)</h4>
 <ul>
 <li>Test problems view with grouping and sorting</li>
 <li>Test quick fix dialog
 <ul><li>With and without multi quick fixes (all quick fixes which are also clean ups are multi quick fixes FAQ: Benno)</li></ul></li>
 </ul>

 <h4>Search view (Markus, Dani) (FAQ: Martin)</h4>
 Test usability/functionability of new Search view

 <h4>template expansion (Benno, Martin) (FAQ: Tom)</h4>
 <p>see  bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=126662">126662</a> and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=71587">71587</a></p>
 Test:
 <ul>
 <li>with different selections: none, single-line, multi-line</li>
 <li>invoke content assist on a selection, then type the name of the template to refine the proposal list</li>
 <li>check that formatting is ok</li>
 </ul>

 <h4>template import export (Tobias, Markus) (FAQ: Tom)</h4>
 See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79805">79805</a>
 <ul>
 <li>import templates</li>
 <li>override the default using the -pluginInitialization command line switch</li>
 <li>ensure pressing the "Defaults" button on the preference page works as expected</li>
 </ul>

 <h4>content assist (Tobias, Martin) (FAQ: Tom)</h4>
 <p>see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=49610">49610</a>
 ensure that inserted completions (java methods, types) conform to the formatter preferences:
 <ul>
 <li>method, type arguments</li>
 <li>parentheses, brackets...</li>
 </ul>


 <br>
 </body>
 </html>
	<!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.2 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.2 M5 Test Grid</h1>
	Test day: Tuesday, 2006-02-14<br>
	Test Build: latest I-build<br>
	Components: JDT/Text, JDT/UI, Platform/Search, Platform/Compare and Platform/Text<br>
	Testers: Martin, Dani, Markus, Tobias, Benno, Tom<br>

	<h4>Goal</h4>
	<ul>
	<li>test new functionality added since M4</li>
	<li>sanity check performance</li>
	<li>verify that severe bugs are correctly fixed</li>
	</ul>

	<h4>Verification of Bugs (ALL)</h4>
	<span style="font-style: italic;">There are 246 so everyone should verify 41. Take high-priority bugs first.<br>
	Before starting to verify add a comment that you take a bug for verification.</span><br>
	<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.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
	JDT UI bugs P1/P2, 3.2M5</a></li>

	<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&component=Compare&priority=P1&priority=P2&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
	Text, Search, and Compare bugs P1/P2, 3.2 M5</a><p></p></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.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
	JDT UI bugs blocker/critical/major, 3.2 M5</a></li>

	<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&component=Compare&bug_severity=blocker&bug_severity=critical&bug_severity=major&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
	Text, Search, and Compare bugs blocker/critical/major, 3.2 M5</a><p></p></li>

	<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&product=JDT&component=UI&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
	all JDT UI bugs 3.2 M5</a></li>

	<li><a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Eclipse&component=Text&component=Search&component=Compare&target_milestone=3.2%20M5&bug_status=RESOLVED&resolution=FIXED&order=bugs.priority,bugs.target_milestone,bugs.bug_id">
	all Text, Search, and Compare bugs 3.2 M5</a><p></p></li>

	</ul>

	<h4>Watch out for cheese and odd behavior in the Text and Java editors (ALL)</h4>
	<p></p>
	<hr/>

	<h4>New clean ups and new Clean Up Wizard UI (Markus, Tobias) (FAQ: Benno)</h4>
	<p>Check wording and test usability of new Clean Up Wizard</p>
	<p>Test new Clean ups:</p>
	<ul>
	<li>Add serial version Id (generated/default)</li>
	<li>Remove unnecessary blocks</li>
	<li>Remove unnecessary casts</li>
	</ul>

	<h4>Build path wizards (Martin, Tom) (FAQ: Benno)</h4>
	<p>Test new build path wizards:
	<ul>
	<li>Link source folder</li>
	<li>Add source folder</li>
	<li>Edit inclusion/exclusion patterns</li>
	</ul>
	By starting the wizards through:
	<ul>
	<li>New Project creation wizard</li>
	<li>Package explorer context menu</li>
	<li>Projects build path properties</li>
	</ul>
	<ul>
	<li>Verify that there is no way to commit an invalide class path</li>
	<li>Check wording</li>
	<li>Test usability</li>
	<li>Test that renaming/removing/adding a source folder works as expected (i.e. that the corresponding files are removed/renamed/added as well)
	</ul>

	<h4>Type selection history (Tom, Markus) (FAQ: Benno)</h4>
	<p>Import types with:</p>
	<ul>
	<li>Code assist</li>
	<li>Organize import</li>
	<li>Add imports</li>
	</ul>
	<p>Verify that:</p>
	<ul>
	<li>Previous selected types are on top of the list if conflicting types</li>
	<li>Selection history is stored between sessions</li>
	</ul>
	<p>Try to find dialogs where it would also make sense to have the same history</p>

	<h4>Package Explorer 1 (Dani, Benno) (FAQ: Dirk)</h4>

	<ul>
	<li>test in workset mode</li>
	<li>create a couple of working sets having the same elements</li>
	<li>structurally change the content of the elements in the working set
	by adding, removing or moving elements.</li>
	</ul>

	<p>Ensure that:</p>
	<ul>
	<li>no elements get lost or rendered more often than they should</li>
	<li>they are rendered under the correct parent</li>
	<li>the selection is kept stable during these changes</li>
	</ul>

	<h4>Package Explorer 2 (Dani, Martin) (FAQ: Benno)</h4>
	<p>Make sure that compilation units are never parsed while exploring the package explorer/resource navigator/java browsing perspective (unless of course the cu needs to be parsed because the cu is expaned)</p>
	<ul>
	<li>Take a large cu (3MB+) watch out for ui freezes</li>
	<li>Test in flat and hierarchical mode</li>
	<li>Open context menu on elements</li>
	</ul>
	<p>See also bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=127105">127105</a></p>

	<h4>Editors (Tobias, Markus) (FAQ: Dani)</h4>
	<ul>
	<li>test Quick Fix in the Properties editor (via menu and via key binding)</li>
	<li>test whether Quick Fix works in the Properties editor (via menu and via key binding)</li>
	<li>test whether Quick Fix works in the Java editor (via menu and via key binding)</li>
	<li>compare two *.properties files - verify that the compare editor opens</li>
	<li>compare two *.java files - verify that the compare editor opens</li>
	<li>test 1 1/2 click in the text and Java editor<br>
	<ul>note: selection is done character by character and not word by word</ul></li>
	</ul>

	<h4>Read only status (Benno, Martin) (FAQ: Dani)</h4>
	<p>verify that the read-only status is correctly shown for:</p>
	<ul>
	<li>read-only *.java files</li>
	<li>*.class files</li>
	<li>types from a JAR</li>
	</ul>

	<h4>Generate hashCode() and equals() (Benno, Tom) (FAQ: Tobias)</h4>

	<ul>
	<li>Verify that correct code is generated</li>
	<li>Verify that warning messages appear in a dialog if either:
	<ul>
	<li>the hashCode()/equals() is not implemented within the classhierarchy</li>
	<li>or the generated would reference a field whose type has
	unimplemented hashCode()/equals() methods.</li></ul></li>
	</ul>

	<h4>JAR Exporter (Markus, Martin) (FAQ: Tobias)</h4>

	<p>Test the export of JAR files with refactoring information</p>

	<p>Verify that the checked refactorings are indeed exported
	(refactorings.xml in the META-INF directory)</p>

	<h4>Replace JAR File (Dani, Tom) (FAQ: Tobias)</h4>
	<ul>
	<li>Test the replace of an existing JAR file on the build path with a new
	one containing refactoring information.</li>
	<li>Test replacing an existing JAR file which contains refactoring
	information with a new one containing the entire project history. The
	refactoring preview should only display the delta which has not yet been
	applied.</li>
	</ul>

	<h4>Refactoring Scripts (Dani, Benno) (FAQ: Tobias)</h4>
	<ul>
	<li>Test the creation and application of arbitrary scripts, containing
	several refactorings</li>
	<li>Verify that correct undos are generated</li>
	</ul>

	<h4>JUnit View History (Tobias, Benno) (FAQ: Markus)</h4>
	<ul>
	<li>test the view with concurrent JUnit Tests and JUnit Plug-in Tests</li>
	<li>test switching from/to running/stopped/finished test runs</li>
	<li>verify that progress is correctly reported in progress bar/counters</li>
	<li>check view icons (shows progress if view is invisible fast view; sensible image when view is visible)</li>
	</ul>

	<h4>Introduce Indirection (Tom, Dani) (FAQ: Markus)</h4>
	<ul>
	<li>test with methods from source and with binary methods (start at an invocation site)</li>
	<li>test with overridden methods</li>
	</ul>

	<h4>Problems view (Tom, Tobias) (FAQ: Martin)</h4>
	<ul>
	<li>Test problems view with grouping and sorting</li>
	<li>Test quick fix dialog
	<ul><li>With and without multi quick fixes (all quick fixes which are also clean ups are multi quick fixes FAQ: Benno)</li></ul></li>
	</ul>

	<h4>Search view (Markus, Dani) (FAQ: Martin)</h4>
	Test usability/functionability of new Search view

	<h4>template expansion (Benno, Martin) (FAQ: Tom)</h4>
	<p>see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=126662">126662</a> and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=71587">71587</a></p>
	Test:
	<ul>
	<li>with different selections: none, single-line, multi-line</li>
	<li>invoke content assist on a selection, then type the name of the template to refine the proposal list</li>
	<li>check that formatting is ok</li>
	</ul>

	<h4>template import export (Tobias, Markus) (FAQ: Tom)</h4>
	See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79805">79805</a>
	<ul>
	<li>import templates</li>
	<li>override the default using the -pluginInitialization command line switch</li>
	<li>ensure pressing the "Defaults" button on the preference page works as expected</li>
	</ul>

	<h4>content assist (Tobias, Martin) (FAQ: Tom)</h4>
	<p>see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=49610">49610</a>
	ensure that inserted completions (java methods, types) conform to the formatter preferences:
	<ul>
	<li>method, type arguments</li>
	<li>parentheses, brackets...</li>
	</ul>



	<br>
	</body>
	</html>