requirements-testing - Revision history

Brian: Reverted edits by LaacpAsdom (Talk) to last version by MarkRickerby

2008-12-20T21:18:27Z

Reverted edits by LaacpAsdom (Talk) to last version by MarkRickerby

← Older revision		Revision as of 21:18, 20 December 2008
Line 1:		Line 1:
	~~dronbascoout~~
	== Requirements Testing Brainstorm ==		== Requirements Testing Brainstorm ==

2008-12-19T18:12:46Z

cnadellig

← Older revision		Revision as of 18:12, 19 December 2008
Line 1:		Line 1:
			dronbascoout
	== Requirements Testing Brainstorm ==		== Requirements Testing Brainstorm ==

2005-12-15T00:43:58Z

← Older revision		Revision as of 00:43, 15 December 2005
Line 73:		Line 73:
	</pre>		</pre>

	This raises some interesting possibilities for both documentation and test generation. As well as functioning as use case documentation, this basic list could be used as input ~~to generate a set of JWebUnit (Java) or Simpletest (PHP) test cases and assertions~~.		This raises some interesting possibilities for both documentation and test generation. As well as functioning as use case documentation, this basic list could be used as input for code generation tools.

2005-12-15T00:42:29Z

@@ Line 1: / Line 1: @@
-== Accceptance Testing Microformat ==
+== Requirements Testing Brainstorm ==
 This is a concept for documenting acceptance tests and project requirements in XHTML. The microformat should exist to encourage and facilitate the progress and uptake of Agile development methodologies across a wide spectrum of projects and organizations.
 == The problem ==
@@ Line 14: / Line 18: @@
 A simple HTML vocabulary could make it much easier to share structured requirements information through a wiki type format, which could thus be updated in realtime to reflect changing requirements and new knowledge about the conditions of a system.
 == Test Vocabulary ==

2005-12-07T22:49:23Z

added short note about feedparser.org/tests

← Older revision		Revision as of 22:49, 7 December 2005
Line 21:		Line 21:

	== Existing Tools and Practice ==		== Existing Tools and Practice ==

			=== Feed Parser Test Suite ===

			The XML files from the [http://feedparser.org/tests/ Feed Parser Test Suite] created by Mark Pilgrim are prefixed with a comment containing a description and expectation, decoupling the test assertions from imperative code:

			<pre>
			<!--
			Description: Atom namespace (official)
			Expect: bozo and feed['title'] == u'Example Atom'
			-->

			<!--
			Description: entry contributor homepage
			Expect: bozo and entries[0]['contributors'][0]['url'] == u'http://example.com/'
			-->
			</pre>

	=== Canoo WebTest ===		=== Canoo WebTest ===

2005-09-22T00:23:51Z

added canoo webtest

← Older revision		Revision as of 00:23, 22 September 2005
Line 21:		Line 21:

	== Existing Tools and Practice ==		== Existing Tools and Practice ==

			=== Canoo WebTest ===

			[http://webtest.canoo.com/manual/WebTestHome.html Canoo WebTest] runs test steps defined in the Ant XML format:

			<pre>
			<target name="login" >
			<webtest name="normal" >
			&config;
			<steps>
			<invoke description="get Login Page"
			url="login.jsp" />
			<verifyTitle description="we should see the login title"
			text="Login Page" />
			<setInputField description="set user name"
			name="username"
			value="scott" />
			<setInputField description="set password"
			name="password"
			value="tiger" />
			<clickButton description="Click the submit button"
			label="let me in" />
			<verifyTitle description="Home Page follows if login ok"
			text="Home Page" />
			</steps>
			</webtest>
			</target>
			</pre>

	=== Selenium ===		=== Selenium ===

2005-08-29T09:48:33Z

expanded existing tool examples

@@ Line 20: / Line 20: @@
 To make use of the full benefits of automated acceptance testing, there needs to be a way to integrate code generation and test reporting directly into a workflow by integrating with the tools that are already being used in the common office environment. FitNesse (wiki based) and Arbiter (document based) tools are two of the steps in this direction. Arbiter uses list items to define test procedures, wheras FitNesse uses tables to define expectations. Apart from that, they work in a very similar way: upload a document/wiki page -> parse the test definitions -> generate the test code -> run the test code -> report back results. But they're still too attached to the concept of a "document" as a separate editable file, rather than a dynamic web resource.
-== Existing Tools ==
+== Existing Tools and Practice ==
 [http://selenium.thoughtworks.com/ Selenium] is a Javascript based testing agent that runs a set of commands on a target website using a mini language for binding actions and assertions to page elements and DOM selections. Basic commands include:
@@ Line 61: / Line 63: @@
 There are no specific semantic attributes used - the test tool simply extracts commands from the columns of the table.
 == Test Vocabulary ==

2005-08-26T04:53:18Z

@@ Line 19: / Line 19: @@
 To make use of the full benefits of automated acceptance testing, there needs to be a way to integrate code generation and test reporting directly into a workflow by integrating with the tools that are already being used in the common office environment. FitNesse (wiki based) and Arbiter (document based) tools are two of the steps in this direction. Arbiter uses list items to define test procedures, wheras FitNesse uses tables to define expectations. Apart from that, they work in a very similar way: upload a document/wiki page -> parse the test definitions -> generate the test code -> run the test code -> report back results. But they're still too attached to the concept of a "document" as a separate editable file, rather than a dynamic web resource.
 == Test Vocabulary ==
-A list of the common actions allowed by a web acceptance testing tool (In this case, Arbiter/Simpletest)
+A list of possible commands for a a web acceptance testing tool in basic English:
 <pre>
   - Start at [link] (Go to [link])

2005-07-20T12:45:23Z

← Older revision		Revision as of 12:45, 20 July 2005
Line 1:		Line 1:
	== ~~About hTest~~ ==		== Accceptance Testing Microformat ==

	~~hTest~~ is a concept for documenting acceptance tests and project requirements in XHTML. ~~It exists~~ to facilitate the progress and uptake of Agile development methodologies across a wide spectrum of projects and organizations.		This is a concept for documenting acceptance tests and project requirements in XHTML. The microformat should exist to encourage and facilitate the progress and uptake of Agile development methodologies across a wide spectrum of projects and organizations.

	== The problem ==		== The problem ==

2005-07-20T12:44:11Z

← Older revision		Revision as of 12:44, 20 July 2005
Line 43:		Line 43:
	</div>		</div>
	</pre>		</pre>

	Some concerns here with duplicating the pass/fail result as inline text in the EM or SPAN with the class existing on the LI. This markup, at least would be compatible with what we're currently reporting from Simpletest.

	== xoTest: XOXO outlines for defining macros ==		== xoTest: XOXO outlines for defining macros ==