jst/components/ws/M4/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="../../../../../" />
 		<title>JST Web Services Tools Milestone 4 Test Plan</title>
 	</head>

 	<body>
 		<h1>JST Web Services Tools Milestone 4 Test Plan</h1>
 		<h2>Status of this Plan</h2>
 		<p>Proposed Plan (4-15-2005)</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>
 			We don't have any official API yet in M4 but will reserve
 			this space for future plans to details where API Unit tests
 			are, their coverage, etc. We will be doing some API unit
 			tests on the internal provisional APIs in m4.
 		</p>

 		<h3>
 			<b>End User Testing</b>
 		</h3>
 		<p>
 			We will be testing the Web Services wizard, Web Services
 			Client wizard, Web Services context menus, Web Services
 			preferences pages and the Web Services Explorer.
 		</p>

 		<p>
 			As we progress through milestones, we'll add more and more
 			specific details to each scenario.
 		</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.
 		</p>

 		<h3>
 			<b>Performance Testing</b>
 		</h3>
 		<p>
 			We are in the process of adding some automated test cases.
 			We will continue to add more test cases in upcoming
 			milestones.
 		</p>

 		<h2>Functionality</h2>
 		<p>
 			Our emphasis for M4 has been on the design of a new
 			provisional API that the community can begin using to extend
 			the Web services platform. Because of our focus on the
 			provisional API and the porting of existing wizards to exploit
 			that provisional API, the implementation and functionality
 			of Web services in M4 is not as stable as it was in M3. See
 			the Test Scenarios section for specific workarounds.
 		</p>
 		<p>
 			Note that because of classloading issues with Tomcat (See
 			defect
 			<a
 				href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91018">
 				91018
 			</a>
 			for more detail), only the WSDL and WSIL functionality of
 			the Web Service Explorer are functional in M4. The UDDI
 			functionality used for the discovery and publishing of a Web
 			service to UDDI is not available in M4.

 		</p>

 		<h2>Test scenarios</h2>
 		<p>
 			For all the scenarios involving the creation and consumption
 			of Axis Web services, the users need to do the following
 			first before running any of the test scenarios with the Web service wizard
 			or Web service client wizard:
 		</p>
 		<ul>
 			<li>Create a server.</li>
 			<li>
 				Create the projects and modules that would contain the
 				Web service or Web service client proxy.
 			</li>
 			<li>Associate the modules with the server.</li>
 			<li>
 				On the Service/Client Configuration Page (page 3),
 				double-check the default values and change them if
 				necessary:
 				<ul>
 					<li>
 						Ensure that the correct server, runtime and J2EE
 						level are selected. If the values are not
 						correct, use the
 						<b>Edit</b>
 						button to pick the correct values.
 					</li>
 					<li>
 						Ensure that the correct project/module are
 						selected.  If the project/module is not
 						correct, use the drop-down combo to pick the
 						right one.
 					</li>
 				</ul>
 			</li>
 		</ul>
 		<p>
 			Note that the Next button is always enabled in the Web Service wizard
 			and Web Service Client wizard. If you are on the last page
 			of the wizard, hitting
 			<b>Next</b>
 			would not do anything and you will have to hit
 			<b>Finish</b>
 			to dismiss the wizard.
 		</p>
 		<p>Here are the scenarios:</p>
 		<h3>
 			<a href="../scenarios/axis_bujava.html">
 				Axis bottom up Java Web services
 			</a>
 		</h3>

 		<h3>
 			<a href="../scenarios/axis_tdjava.html">
 				Axis top down Java Web services
 			</a>
 		</h3>

 		<h3>
 			<a href="../scenarios/axis_cjava.html">
 				Axis Web Service client Java proxy
 			</a>
 		</h3>

 		<h3>
 			<a href="../scenarios/wse.html">Web Service Explorer</a>
 		</h3>

 		<h3>
 			<a href="../scenarios/popups.html">
 				Web Service context menus
 			</a>
 		</h3>

 		<h3>
 			<a href="../scenarios/prefs.html">
 				Web Services preferences
 			</a>
 		</h3>

 		<h3>
 			<a href="../scenarios/dwf.html">Dynamic Wizard Framework</a>
 		</h3>

 	</body>
 </html>
	<?xml version="1.0" encoding="UTF-8"?>
	<?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?>
	<html>
	<head>
	<meta name="root" content="../../../../../" />
	<title>JST Web Services Tools Milestone 4 Test Plan</title>
	</head>

	<body>
	<h1>JST Web Services Tools Milestone 4 Test Plan</h1>
	<h2>Status of this Plan</h2>
	<p>Proposed Plan (4-15-2005)</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>
	We don't have any official API yet in M4 but will reserve
	this space for future plans to details where API Unit tests
	are, their coverage, etc. We will be doing some API unit
	tests on the internal provisional APIs in m4.
	</p>

	<h3>
	<b>End User Testing</b>
	</h3>
	<p>
	We will be testing the Web Services wizard, Web Services
	Client wizard, Web Services context menus, Web Services
	preferences pages and the Web Services Explorer.
	</p>

	<p>
	As we progress through milestones, we'll add more and more
	specific details to each scenario.
	</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.
	</p>

	<h3>
	<b>Performance Testing</b>
	</h3>
	<p>
	We are in the process of adding some automated test cases.
	We will continue to add more test cases in upcoming
	milestones.
	</p>

	<h2>Functionality</h2>
	<p>
	Our emphasis for M4 has been on the design of a new
	provisional API that the community can begin using to extend
	the Web services platform. Because of our focus on the
	provisional API and the porting of existing wizards to exploit
	that provisional API, the implementation and functionality
	of Web services in M4 is not as stable as it was in M3. See
	the Test Scenarios section for specific workarounds.
	</p>
	<p>
	Note that because of classloading issues with Tomcat (See
	defect
	<a
	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=91018">
	91018
	</a>
	for more detail), only the WSDL and WSIL functionality of
	the Web Service Explorer are functional in M4. The UDDI
	functionality used for the discovery and publishing of a Web
	service to UDDI is not available in M4.

	</p>

	<h2>Test scenarios</h2>
	<p>
	For all the scenarios involving the creation and consumption
	of Axis Web services, the users need to do the following
	first before running any of the test scenarios with the Web service wizard
	or Web service client wizard:
	</p>
	<ul>
	<li>Create a server.</li>
	<li>
	Create the projects and modules that would contain the
	Web service or Web service client proxy.
	</li>
	<li>Associate the modules with the server.</li>
	<li>
	On the Service/Client Configuration Page (page 3),
	double-check the default values and change them if
	necessary:
	<ul>
	<li>
	Ensure that the correct server, runtime and J2EE
	level are selected. If the values are not
	correct, use the
	<b>Edit</b>
	button to pick the correct values.
	</li>
	<li>
	Ensure that the correct project/module are
	selected. If the project/module is not
	correct, use the drop-down combo to pick the
	right one.
	</li>
	</ul>
	</li>
	</ul>
	<p>
	Note that the Next button is always enabled in the Web Service wizard
	and Web Service Client wizard. If you are on the last page
	of the wizard, hitting
	<b>Next</b>
	would not do anything and you will have to hit
	<b>Finish</b>
	to dismiss the wizard.
	</p>
	<p>Here are the scenarios:</p>
	<h3>
	<a href="../scenarios/axis_bujava.html">
	Axis bottom up Java Web services
	</a>
	</h3>

	<h3>
	<a href="../scenarios/axis_tdjava.html">
	Axis top down Java Web services
	</a>
	</h3>

	<h3>
	<a href="../scenarios/axis_cjava.html">
	Axis Web Service client Java proxy
	</a>
	</h3>

	<h3>
	<a href="../scenarios/wse.html">Web Service Explorer</a>
	</h3>

	<h3>
	<a href="../scenarios/popups.html">
	Web Service context menus
	</a>
	</h3>

	<h3>
	<a href="../scenarios/prefs.html">
	Web Services preferences
	</a>
	</h3>

	<h3>
	<a href="../scenarios/dwf.html">Dynamic Wizard Framework</a>
	</h3>

	</body>
	</html>