wst/components/html/M5/milestone_test_plan.xml - 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="../../../../../" />
 		<title>WTP Milestone 5</title>
 	</head>
 	<body>
 		<h1>HTML Test Plan</h1>
 		<h2>Status of this Plan</h2>
 		<p>Proposed Plan (6.27.05)</p>

 		<h2>Overall goals</h2>
 		<h3><b>New for M5</b></h3>
 		<p>
 			Not much has been added in terms of new functionality
 			for M5.  Most of the work done was in the areas of
 			refactoring, cleaning up dead code, and cleaning up APIs.
 			Also more unit tests were added which are run regularly
 			with the build.
 		</p>
 		<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 M5 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 M5, 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>HTML Tests</h2>
 		<ul>
 			<li>check Source Editing features from the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a></li>
 			<li>
 				check &quot;embedded languages&quot; (CSS, JavaScript)
 				have same features as indicated in the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a>
 			</li>
 			<li>
 				A quick sanity check that preferences have effect, and
 				do no harm. Only quick check, since many changes planned
 				in this are for future milestones.
 			</li>
 		</ul>
 	<p>
 			<ul>
 				<li>
 					as you type validation:
 					<ul>
 						<li>
 							job based, make sure squiggles show up when
 							they should and are removed when problems
 							are fixed
 						</li>
 						<li>
 							test various partition types in the document
 						</li>

 					</ul>
 				</li>
 				<li>
 					html validation:
 					<ul>
 						<li>batch workbench validation, as-you-type</li>
 					</ul>
 				</li>

 				<li>
 					hyperlink open on:
 					<ul>
 						<li>Java Elements, href, includes, link, style, etc...</li>
 					</ul>
 				</li>

 				<li>
 					preferences:
 					<ul>
 						<li>how we use the preferences in the "All Text Editors"
 					         preference page now.
 					    </li>
 						<li>make sure preferenes work</li>
 						<li>after shutdown and restart</li>
 					</ul>
 				</li>

 				<li>
 					run performance unit tests:
 					<ul>
 						<li>
 							record results for comparison with future
 							milestones
 						</li>
 					</ul>
 				</li>

 				<li>
 					profiling:
 					<ul>
 						<li>using your favorite profiler (<a href="http://eclipsefaq.org/chris/xray/index.html">XRay</a>, YourKit, etc...)
 						    test basic editor functions and look for
 							problem areas (large memory consumption, intense CPU usage)
 						</li>
 					</ul>
 				</li>

 			</ul>
 		</p>
 		<h2>XHTML Tests</h2>
 		<ul>
 			<li>check Source Editing features from the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a></li>
 			<li>
 				check &quot;embedded languages&quot; (CSS, JavaScript)
 				have same features as indicated in the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a>.
 			</li>
 			<li>
 				Check that the standard different doctypes give
 				different, correct content assist.
 			</li>
 			<li>
 				A quick sanity check that preferences have effect, and
 				do no harm. Only quick check, since many changes planned
 				in this are for future milestones.
 			</li>
 		</ul>

 		<h2>New for M5</h2>
 <p>
 	Tab Preferences
 </p>
 <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>

 		<h2><b>Regression Tests</b></h2>
 		<p>
 			<a href="../../../../wst/components/sse/M4/formatting-test.html">Formatting tests</a>
 			<br/>
 		</p>

 		<h2>Source Editing Test Plans</h2>
 		<p>
 			<a href="../../../../wst/components/sse/M5/milestone_test_plan.html">org.eclipse.wst.sse</a>
 			<br/><a href="../../../../wst/components/xml/M5/milestone_test_plan.html">org.eclipse.wst.xml</a>
 			<br/><a href="../../../../wst/components/html/M5/milestone_test_plan.html">org.eclipse.wst.html</a>
 			<br/><a href="../../../../wst/components/css/M5/milestone_test_plan.html">org.eclipse.wst.css</a>
 			<br/><a href="../../../../wst/components/dtd/M5/milestone_test_plan.html">org.eclipse.wst.dtd</a>
 			<br/><a href="../../../../wst/components/javascript/M5/milestone_test_plan.html">org.eclipse.wst.javascript</a>

 			<br/><a href="../../../../jst/components/jsp/M5/milestone_test_plan.html">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="../../../../../" />
	<title>WTP Milestone 5</title>
	</head>
	<body>
	<h1>HTML Test Plan</h1>
	<h2>Status of this Plan</h2>
	<p>Proposed Plan (6.27.05)</p>

	<h2>Overall goals</h2>
	<h3><b>New for M5</b></h3>
	<p>
	Not much has been added in terms of new functionality
	for M5. Most of the work done was in the areas of
	refactoring, cleaning up dead code, and cleaning up APIs.
	Also more unit tests were added which are run regularly
	with the build.
	</p>
	<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 M5 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 M5, 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>HTML Tests</h2>
	<ul>
	<li>check Source Editing features from the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a></li>
	<li>
	check "embedded languages" (CSS, JavaScript)
	have same features as indicated in the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a>
	</li>
	<li>
	A quick sanity check that preferences have effect, and
	do no harm. Only quick check, since many changes planned
	in this are for future milestones.
	</li>
	</ul>
	<p>
	<ul>
	<li>
	as you type validation:
	<ul>
	<li>
	job based, make sure squiggles show up when
	they should and are removed when problems
	are fixed
	</li>
	<li>
	test various partition types in the document
	</li>

	</ul>
	</li>
	<li>
	html validation:
	<ul>
	<li>batch workbench validation, as-you-type</li>
	</ul>
	</li>

	<li>
	hyperlink open on:
	<ul>
	<li>Java Elements, href, includes, link, style, etc...</li>
	</ul>
	</li>

	<li>
	preferences:
	<ul>
	<li>how we use the preferences in the "All Text Editors"
	preference page now.
	</li>
	<li>make sure preferenes work</li>
	<li>after shutdown and restart</li>
	</ul>
	</li>

	<li>
	run performance unit tests:
	<ul>
	<li>
	record results for comparison with future
	milestones
	</li>
	</ul>
	</li>

	<li>
	profiling:
	<ul>
	<li>using your favorite profiler (<a href="http://eclipsefaq.org/chris/xray/index.html">XRay</a>, YourKit, etc...)
	test basic editor functions and look for
	problem areas (large memory consumption, intense CPU usage)
	</li>
	</ul>
	</li>

	</ul>
	</p>
	<h2>XHTML Tests</h2>
	<ul>
	<li>check Source Editing features from the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a></li>
	<li>
	check "embedded languages" (CSS, JavaScript)
	have same features as indicated in the <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a>.
	</li>
	<li>
	Check that the standard different doctypes give
	different, correct content assist.
	</li>
	<li>
	A quick sanity check that preferences have effect, and
	do no harm. Only quick check, since many changes planned
	in this are for future milestones.
	</li>
	</ul>

	<h2>New for M5</h2>
	<p>
	Tab Preferences
	</p>
	<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>

	<h2><b>Regression Tests</b></h2>
	<p>
	<a href="../../../../wst/components/sse/M4/formatting-test.html">Formatting tests</a>
	<br/>
	</p>

	<h2>Source Editing Test Plans</h2>
	<p>
	<a href="../../../../wst/components/sse/M5/milestone_test_plan.html">org.eclipse.wst.sse</a>
	<br/><a href="../../../../wst/components/xml/M5/milestone_test_plan.html">org.eclipse.wst.xml</a>
	<br/><a href="../../../../wst/components/html/M5/milestone_test_plan.html">org.eclipse.wst.html</a>
	<br/><a href="../../../../wst/components/css/M5/milestone_test_plan.html">org.eclipse.wst.css</a>
	<br/><a href="../../../../wst/components/dtd/M5/milestone_test_plan.html">org.eclipse.wst.dtd</a>
	<br/><a href="../../../../wst/components/javascript/M5/milestone_test_plan.html">org.eclipse.wst.javascript</a>

	<br/><a href="../../../../jst/components/jsp/M5/milestone_test_plan.html">org.eclipse.jst.jsp</a>
	</p>
	</body>
	</html>