plans/2.0/wst/javascript/test_plan.xml - gerrit/www.eclipse.org/webtools - Git at Google

 <?xml version="1.0" encoding="utf-8"?>
 <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?>
 <html>
     <head>
         <meta name="root" content="../../../www/" />
         <title>javascript wtp 2.0 final test plan</title>
     </head>
     <body>
         <h1>javascript wtp 2.0 final test plan</h1>
         <h2>Status of this Plan</h2>
         <p>Proposed Plan (5.14.07)</p>

         <h2>Overall goals</h2>
         <h3>
             <b>Co-developer Testing</b>
         </h3>
         <p>
             We will inspect &quot;runtime&quot; version of build to be
             sure extra source is not included, and more important, we'll
             inspect and test importing SDK version to be sure all
             relevant &quot;open source&quot; is included in that SDK
             build and that it correctly imports into a development
             environment.
         </p>
         <h3>
             <b>API Testing</b>
         </h3>
         <p>
             Here in 2.0 we don't consider we have any official API yet
             (since not spec'd as such) but will reserve this space for
             future plans to details were API Unit tests are, their
             coverage, etc.
         </p>
         <p>
             We do have several hundred unit tests which we expect to be
             running and passing for 2.0, which test various aspects of
             parsing, model creation, and correct charset handling, among
             other things.
         </p>

         <h3>
             <b>End User Testing</b>
         </h3>
         <p>
             The nature of the end-user testing is intentionally planned
             to be "ad hoc" instead of specifying step by step "how to"
             directions and specific "expected results" sections often
             seen in test cases. This is done because its felt leads to
             greater number of "paths" being tested, and allows end-users
             more motivation for logging "bugs" if things didn't work as
             <i>they</i>
             expected, even if it is working as designed.
         </p>

         <p>
             As we progress through milestones, we'll add more and more
             detail for special cases, special files, special projects,
             etc.When we do have special or sample test files and
             projects, we will keep those stored in CVS, as projects
             under a
             <i>testdata</i>
             directory under the
             <i>development</i>
             directory of relevant component so that testers (from
             immediate team, or community) can easily check out into the
             environment being tested.
         </p>

         <h3>
             <b>Platform Testing</b>
         </h3>
         <p>
             While we do not have any platform specific code, or
             function, we will have some team members do end-user tests
             on Linux, some on Windows. We will also confirm unit tests
             pass on both platforms.
         </p>

         <h3>
             <b>Performance Testing</b>
         </h3>
         <p>
             We have added (some) automated performance tests along the
             lines of the Eclipse base performance unit tests in future
             milestones. These are currently in the
             <b>org.eclipse.wst.*.ui.tests.performance</b>
             and
             <b>org.eclipse.jst.jsp.ui.tests.performance</b>
             plugins.
             <br />
             <br />
             We will continue to add more test cases in upcoming
             milestones.
         </p>
         <h2>Testing focus for 2.0</h2>
         <ul>
             <li>Verify quick fix for spelling mistakes works</li>
             <li>
                 Preferences:
                 <ul>
                     <li>
                         Syntax highlighting preferences:
                         <ul>
                             <li>
                                 Verify font styles (bold, italics,
                                 strikethrough, etc) are obeyed
                             </li>
                             <li>
                                 Verify background syntax color
                                 preference is followed
                             </li>
                         </ul>
                     </li>
                     <li>Verify keywords for preference pages works</li>
                     <li>
                         Verify text editor's smart home/end caret
                         positioning preference is followed
                     </li>
                     <li>
                         Verify content assist proposal
                         background/foreground color preferences in
                         structured text editor's preference page are
                         followed
                     </li>
                 </ul>
             </li>
             <li>
                 Verify content assist works correctly (verify icons in
                 content assist proposals look correct)
             </li>
         </ul>
         <h2>JavaScript Tests</h2>
         <ul>
             <li>
                 Check Source Editing features from feature
                 <a href="../sse/test_plan.php#matrix">feature matrix</a>
             </li>
             <li>
                 Test Design page, Source page, Outline view, Properties
                 view synchronization
             </li>
             <li>
                 Preferences:
                 <ul>
                     <li>
                         Test our editors follow preferences in the "All
                         Text Editors" preference page
                     </li>
                     <li>
                         Check that editors follow content type specific
                         preferences under Web and XML preference pages
                     </li>
                     <li>
                         Make sure editors (already open and closed and
                         reopened) are updated when preferences change
                     </li>
                     <li>
                         Check preferences are saved when shutdown and
                         restart workbench
                     </li>
                 </ul>
             </li>

             <li>
                 Tab preferences:
                 <ul>
                     <li>
                         Web and XML-&gt;Content Type Files -&gt; Content
                         Type Source -&gt; Indent using tabs / Indent
                         using spaces -&gt; Indentation size
                     </li>

                     <li>Verify the correct tab character is used</li>
                     <li>
                         Verify the correct number of tab characters is
                         used
                     </li>
                     <li>
                         Verify Source-&gt;Shift Left/Shift Right and the
                         Shift-Tab/Tab key follow the preferences
                     </li>
                     <li>With nothing selected</li>
                     <li>With multiple lines selected</li>
                     <li>Verify Format follow the preferences</li>
                     <li>
                         Verify when using tab characters, the displayed
                         tab width preference is followed
                         (General-&gt;Editors-&gt;Text Editors -&gt;
                         Displayed tab width)
                     </li>
                 </ul>
             </li>
         </ul>
         <li>
             New File Wizard:
             <ul>
                 <li>make sure the template creates a valid file</li>
                 <li>
                     Verify not entering an extension will generate a new
                     file with the default file extension you specified
                     in the preference.
                 </li>
                 <li>
                     Verify entering a file name that already exists
                     without the extension will still give you an error
                     saying the file already exists (for example, if
                     index.jsp already exists, typing "index" will tell
                     you that it already exists)
                 </li>
                 <li>
                     Verify entering a file name with valid/invalid
                     extension still works
                 </li>
             </ul>
         </li>
         <h2>
             <b>Regression Tests</b>
         </h2>
         <p>
             <a
                 href="../../../../wst/components/sse/tests/viewerconfig-test.html">
                 Structured Text Viewer Configuration tests
             </a>
             <br />
             <a
                 href="../../../../wst/components/sse/tests/action-test.html">
                 Structured Text Editor Action tests
             </a>
             <br />
         </p>

         <h2>Source Editing Test Plans</h2>
         <p>
             <a href="../sse/test_plan.php">org.eclipse.wst.sse</a>
             <br />
             <a href="../xml/test_plan.php">org.eclipse.wst.xml</a>
             <br />
             <a href="../html/test_plan.php">org.eclipse.wst.html</a>
             <br />
             <a href="../css/test_plan.php">org.eclipse.wst.css</a>
             <br />
             <a href="../dtd/test_plan.php">org.eclipse.wst.dtd</a>
             <br />
             <a href="../javascript/test_plan.php">
                 org.eclipse.wst.javascript
             </a>
             <br />
             <a href="../../jst/jsp/test_plan.php">
                 org.eclipse.jst.jsp
             </a>
         </p>
     </body>
 </html>
	<?xml version="1.0" encoding="utf-8"?>
	<?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?>
	<html>
	<head>
	<meta name="root" content="../../../www/" />
	<title>javascript wtp 2.0 final test plan</title>
	</head>
	<body>
	<h1>javascript wtp 2.0 final test plan</h1>
	<h2>Status of this Plan</h2>
	<p>Proposed Plan (5.14.07)</p>

	<h2>Overall goals</h2>
	<h3>
	<b>Co-developer Testing</b>
	</h3>
	<p>
	We will inspect "runtime" version of build to be
	sure extra source is not included, and more important, we'll
	inspect and test importing SDK version to be sure all
	relevant "open source" is included in that SDK
	build and that it correctly imports into a development
	environment.
	</p>
	<h3>
	<b>API Testing</b>
	</h3>
	<p>
	Here in 2.0 we don't consider we have any official API yet
	(since not spec'd as such) but will reserve this space for
	future plans to details were API Unit tests are, their
	coverage, etc.
	</p>
	<p>
	We do have several hundred unit tests which we expect to be
	running and passing for 2.0, which test various aspects of
	parsing, model creation, and correct charset handling, among
	other things.
	</p>

	<h3>
	<b>End User Testing</b>
	</h3>
	<p>
	The nature of the end-user testing is intentionally planned
	to be "ad hoc" instead of specifying step by step "how to"
	directions and specific "expected results" sections often
	seen in test cases. This is done because its felt leads to
	greater number of "paths" being tested, and allows end-users
	more motivation for logging "bugs" if things didn't work as
	<i>they</i>
	expected, even if it is working as designed.
	</p>

	<p>
	As we progress through milestones, we'll add more and more
	detail for special cases, special files, special projects,
	etc.When we do have special or sample test files and
	projects, we will keep those stored in CVS, as projects
	under a
	<i>testdata</i>
	directory under the
	<i>development</i>
	directory of relevant component so that testers (from
	immediate team, or community) can easily check out into the
	environment being tested.
	</p>

	<h3>
	<b>Platform Testing</b>
	</h3>
	<p>
	While we do not have any platform specific code, or
	function, we will have some team members do end-user tests
	on Linux, some on Windows. We will also confirm unit tests
	pass on both platforms.
	</p>

	<h3>
	<b>Performance Testing</b>
	</h3>
	<p>
	We have added (some) automated performance tests along the
	lines of the Eclipse base performance unit tests in future
	milestones. These are currently in the
	<b>org.eclipse.wst.*.ui.tests.performance</b>
	and
	<b>org.eclipse.jst.jsp.ui.tests.performance</b>
	plugins.
	<br />
	<br />
	We will continue to add more test cases in upcoming
	milestones.
	</p>
	<h2>Testing focus for 2.0</h2>
	<ul>
	<li>Verify quick fix for spelling mistakes works</li>
	<li>
	Preferences:
	<ul>
	<li>
	Syntax highlighting preferences:
	<ul>
	<li>
	Verify font styles (bold, italics,
	strikethrough, etc) are obeyed
	</li>
	<li>
	Verify background syntax color
	preference is followed
	</li>
	</ul>
	</li>
	<li>Verify keywords for preference pages works</li>
	<li>
	Verify text editor's smart home/end caret
	positioning preference is followed
	</li>
	<li>
	Verify content assist proposal
	background/foreground color preferences in
	structured text editor's preference page are
	followed
	</li>
	</ul>
	</li>
	<li>
	Verify content assist works correctly (verify icons in
	content assist proposals look correct)
	</li>
	</ul>
	<h2>JavaScript Tests</h2>
	<ul>
	<li>
	Check Source Editing features from feature
	<a href="../sse/test_plan.php#matrix">feature matrix</a>
	</li>
	<li>
	Test Design page, Source page, Outline view, Properties
	view synchronization
	</li>
	<li>
	Preferences:
	<ul>
	<li>
	Test our editors follow preferences in the "All
	Text Editors" preference page
	</li>
	<li>
	Check that editors follow content type specific
	preferences under Web and XML preference pages
	</li>
	<li>
	Make sure editors (already open and closed and
	reopened) are updated when preferences change
	</li>
	<li>
	Check preferences are saved when shutdown and
	restart workbench
	</li>
	</ul>
	</li>

	<li>
	Tab preferences:
	<ul>
	<li>
	Web and XML->Content Type Files -> Content
	Type Source -> Indent using tabs / Indent
	using spaces -> Indentation size
	</li>

	<li>Verify the correct tab character is used</li>
	<li>
	Verify the correct number of tab characters is
	used
	</li>
	<li>
	Verify Source->Shift Left/Shift Right and the
	Shift-Tab/Tab key follow the preferences
	</li>
	<li>With nothing selected</li>
	<li>With multiple lines selected</li>
	<li>Verify Format follow the preferences</li>
	<li>
	Verify when using tab characters, the displayed
	tab width preference is followed
	(General->Editors->Text Editors ->
	Displayed tab width)
	</li>
	</ul>
	</li>
	</ul>
	<li>
	New File Wizard:
	<ul>
	<li>make sure the template creates a valid file</li>
	<li>
	Verify not entering an extension will generate a new
	file with the default file extension you specified
	in the preference.
	</li>
	<li>
	Verify entering a file name that already exists
	without the extension will still give you an error
	saying the file already exists (for example, if
	index.jsp already exists, typing "index" will tell
	you that it already exists)
	</li>
	<li>
	Verify entering a file name with valid/invalid
	extension still works
	</li>
	</ul>
	</li>
	<h2>
	<b>Regression Tests</b>
	</h2>
	<p>
	<a
	href="../../../../wst/components/sse/tests/viewerconfig-test.html">
	Structured Text Viewer Configuration tests
	</a>
	<br />
	<a
	href="../../../../wst/components/sse/tests/action-test.html">
	Structured Text Editor Action tests
	</a>
	<br />
	</p>

	<h2>Source Editing Test Plans</h2>
	<p>
	<a href="../sse/test_plan.php">org.eclipse.wst.sse</a>
	<br />
	<a href="../xml/test_plan.php">org.eclipse.wst.xml</a>
	<br />
	<a href="../html/test_plan.php">org.eclipse.wst.html</a>
	<br />
	<a href="../css/test_plan.php">org.eclipse.wst.css</a>
	<br />
	<a href="../dtd/test_plan.php">org.eclipse.wst.dtd</a>
	<br />
	<a href="../javascript/test_plan.php">
	org.eclipse.wst.javascript
	</a>
	<br />
	<a href="../../jst/jsp/test_plan.php">
	org.eclipse.jst.jsp
	</a>
	</p>
	</body>
	</html>