test-fixture - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:33:12Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:33, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Test Fixture~~</entry-title>~~		{{DISPLAYTITLE:Test Fixture}}

	== Introduction ==		== Introduction ==

Barnabywalters: updated with mf2 examples, properties for test-suite, test-fixture and test-assert

2013-10-04T18:05:24Z

updated with mf2 examples, properties for test-suite, test-fixture and test-assert

@@ Line 1: / Line 1: @@
 <entry-title>Test Fixture</entry-title>
-==Introduction==
+== Introduction ==
-The test-fixture is a description of a group of software tests. It is designed as a [[poshformat]], as it has not been through the microformats design and community review [[process]].
+h-x-test-suite is a '''draft''' microformat for publishing code testing data on the web. It’s the [[microformats2]] version of the test-fixture [[poshformat]]. Neither have been through the microformats design and community review [[process]].
-This format was orginal developed for the [http://www.ufxtract.com/testsuite/ UfXtract test-suite] but is now public domain. This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.
+The test-suite is a description of a group software tests. These test are embedded into HTML using as POSH pattern based on microformats2. Each test-suite can contain a number of test-fixture, which are the individual test.
 ==Structure==

Tantek: add see also section, note value-class-date-time-tests all use text-fixture markup

2009-07-07T01:39:49Z

add see also section, note value-class-date-time-tests all use text-fixture markup

← Older revision		Revision as of 01:39, 7 July 2009
Line 182:		Line 182:
	* IsFalse()		* IsFalse()
	* HasProperty()		* HasProperty()

			== see also ==
			* [[test-suite]]
			* [[value-class-date-time-tests]] - which lists a bunch of test cases all marked up with the test-fixture poshformat
			* [[poshformats]]

GlennJones: /* Embeding tests */ corrected coding error

2009-06-29T21:01:28Z

Embeding tests: corrected coding error

← Older revision		Revision as of 21:01, 29 June 2009
Line 169:		Line 169:
	</div>		</div>
	</div>		</div>
	</~~pre~~></~~nowiki~~>		</nowiki></pre>

	Some parsers such as UfXtarct and Sumo already have this ability to parse only a fragement of HTML from a pgae, for other you can use a [http://www.ufxtract.com/proxies/proxy.aspx proxy service]. It allows you to define a URL of a page and the ID of any element and it returns a HTML page containing just that element.		Some parsers such as UfXtarct and Sumo already have this ability to parse only a fragement of HTML from a pgae, for other you can use a [http://www.ufxtract.com/proxies/proxy.aspx proxy service]. It allows you to define a URL of a page and the ID of any element and it returns a HTML page containing just that element.

GlennJones: /* Embeding tests */ Added example of test

2009-06-29T21:00:30Z

Embeding tests: Added example of test

@@ Line 151: / Line 151: @@
 == Embeding tests ==
-When testing microformats you can embed them into the same page as the test-fixture. As the test-fixture itself contains microformats such as hCards so we need to define what section of the page to we should be testing. For the sake of consistency within the microformats test-suite all microformats that are been tested should be contain in a HTML element with the id “uf”.
+You can embed the test microformat into the same page as the test-fixture. As the test-fixture itself contains microformats such as hCards so we need to define what section of the page to we should be testing. For the sake of consistency within the microformats test-suite all microformats that are been tested should be contain in a HTML element with the id “uf”.
 Some parsers such as UfXtarct and Sumo already have this ability to parse only a fragement of HTML from a pgae, for other you can use a [http://www.ufxtract.com/proxies/proxy.aspx proxy service]. It allows you to define a URL of a page and the ID of any element and it returns a HTML page containing just that element.
 == Current test methods ==

GlennJones: Correction and addtional urls

2009-06-29T20:55:07Z

Correction and addtional urls

← Older revision		Revision as of 20:55, 29 June 2009
Line 2:		Line 2:

	==Introduction==		==Introduction==
	The test-fixture is a description of a group of software tests. It is designed as a [[poshformat]], as it has not been through the microformats design and community review [[process]]. The idea is to build a series of pages containing test-fixtures into a full test-suite. ~~This format was orginal developed for the [http://www.ufxtract.com/testsuite/ UfXtract test-suite] but is now public domain.~~		The test-fixture is a description of a group of software tests. It is designed as a [[poshformat]], as it has not been through the microformats design and community review [[process]].
			The idea is to build a series of pages containing test-fixtures into a full test-suite.

	This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.		This format was orginal developed for the [http://www.ufxtract.com/testsuite/ UfXtract test-suite] but is now public domain. This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.

	==Structure==		==Structure==
Line 46:		Line 47:
	* '''<code class="class-name">history</code>''':: The history of changes to test-fixture, as [[hCalendar]] events		* '''<code class="class-name">history</code>''':: The history of changes to test-fixture, as [[hCalendar]] events

			== Example mark up ==
			<pre><nowiki>
			<div class="test-fixture">

	~~<pre><nowiki>~~
	<h1 class="summary">hCard 1 - single occurrence test</h1>		<h1 class="summary">hCard 1 - single occurrence test</h1>
	<p class="description">		<p class="description">
Line 68:		Line 71:
	</ul>		</ul>
	</p>		</p>


	<p>Tests:</p>		<p>Tests:</p>
Line 74:		Line 76:
	<thead>		<thead>
	<tr>		<tr>
	<th>Test</th>		<th>Test</th>
	<th>Result</th>		<th>Result</th>
	<th>Comment</th>		<th>Comment</th>
	</tr>		</tr>
	</thead>		</thead>
	<tbody>		<tbody>
	<tr class="assert">		<tr class="assert">
	<td class="test">vcard[0].fn</td>		<td class="test">vcard[0].fn</td>
	<td class="result">IsEqualTo("John Doe")</td>		<td class="result">IsEqualTo("John Doe")</td>
Line 132:		Line 134:
	</tbody>		</tbody>
	</table>		</table>


	<p>History:</p>		<p>History:</p>
	<ul>		<ul>
Line 143:		Line 144:
	</li>		</li>
	</ul>		</ul>



	</div>		</div>

	</nowiki></pre>		</nowiki></pre>


	== Embeding ~~microformats to test within the same page~~ ==		== Embeding tests ==

	When testing microformats you can embed them into the same page as the test-fixture. As the test-fixture itself contains microformats such as hCards so we need to define what section of the page to we should be testing. For the sake of consistency within the microformats test-suite all microformats ~~That~~ are been tested should be contain in a HTML element with the id “uf”.		When testing microformats you can embed them into the same page as the test-fixture. As the test-fixture itself contains microformats such as hCards so we need to define what section of the page to we should be testing. For the sake of consistency within the microformats test-suite all microformats that are been tested should be contain in a HTML element with the id “uf”.

	Some parsers such as UfXtarct and Sumo already have this ability to parse only a fragement of HTML from a pgae, for other you can use a ~~simple~~ proxy service. It allows you to define a URL of a page and the ID of any element and it returns a HTML page containing just that element.		Some parsers such as UfXtarct and Sumo already have this ability to parse only a fragement of HTML from a pgae, for other you can use a [http://www.ufxtract.com/proxies/proxy.aspx proxy service]. It allows you to define a URL of a page and the ID of any element and it returns a HTML page containing just that element.

Tantek: corrected use of POSH pattern to poshformat - which is really what this is.

2009-06-29T20:26:27Z

corrected use of POSH pattern to poshformat - which is really what this is.

← Older revision		Revision as of 20:26, 29 June 2009
Line 1:		Line 1:
	= Test Fixture =		<entry-title>Test Fixture</entry-title>

	==Introduction==		==Introduction==
	The test-fixture is a description of a group of software tests. It is designed as a ~~microformat~~, ~~but~~ as it has not been through the community review ~~process, it is called a~~ [[~~POSH~~]] ~~pattern~~. The idea is to build a series of pages containing test-fixtures into a full test-suite. This format was orginal developed for the [http://www.ufxtract.com/testsuite/ UfXtract test-suite] but is now public domain.		The test-fixture is a description of a group of software tests. It is designed as a [[poshformat]], as it has not been through the microformats design and community review [[process]]. The idea is to build a series of pages containing test-fixtures into a full test-suite. This format was orginal developed for the [http://www.ufxtract.com/testsuite/ UfXtract test-suite] but is now public domain.

	This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.		This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.

GlennJones: /* Introduction */ Added hyperlinks

2009-06-29T20:16:35Z

Introduction: Added hyperlinks

← Older revision		Revision as of 20:16, 29 June 2009
Line 2:		Line 2:

	==Introduction==		==Introduction==
	The test-fixture is a description of a group of software tests. It is designed as a microformat, but as it has not been through the community review process, it is called a POSH pattern. The idea is to build a series of pages containing test-fixtures into a full test-suite. This format was orginal developed for the UfXtract test-suite but is now public domain.		The test-fixture is a description of a group of software tests. It is designed as a microformat, but as it has not been through the community review process, it is called a [[POSH]] pattern. The idea is to build a series of pages containing test-fixtures into a full test-suite. This format was orginal developed for the [http://www.ufxtract.com/testsuite/ UfXtract test-suite] but is now public domain.

	~~This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.~~

			This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.

	==Structure==		==Structure==

GlennJones: New page: = Test Fixture = ==Introduction== The test-fixture is a description of a group of software tests. It is designed as a microformat, but as it has not been through the community review proc...

2009-06-29T20:10:07Z

New page: = Test Fixture = ==Introduction== The test-fixture is a description of a group of software tests. It is designed as a microformat, but as it has not been through the community review proc...

New page

= Test Fixture =

==Introduction==
The test-fixture is a description of a group of software tests. It is designed as a microformat, but as it has not been through the community review process, it is called a POSH pattern. The idea is to build a series of pages containing test-fixtures into a full test-suite. This format was orginal developed for the UfXtract test-suite but is now public domain.

This specification should be considered a draft. Contents are subject to change. It is provided here for reference and as a basis for discussion and ongoing development.

==Structure==
* class="'''test-fixture'''"
** class="summary"
** class="''description''"
** class="'''format'''"
** class="''author''" (hcard)
** class="''output''"
*** class="type" [JSON,XML]
*** class="value"
** class="assert"
*** class="test"
*** class="result"
*** class="comment"
** class="''history''" (vevent)

Key
* '''Single occurrence required'''
* Single occurrence optional
* ''Zero or More occurrences''

==Properties==

=== Field details ===
The fields of the test-fixture schema represent the following:

* '''<code class="class-name">test-fixture</code>''':: The root class name
* '''<code class="class-name">summary</code>''':: The title of the test-fixture
* '''<code class="class-name">description</code>''':: An expanded piece of text about the test-fixture
* '''<code class="class-name">format</code>''':: The format to be tested ie hCard
* '''<code class="class-name">author</code>''':: The authors of the test as an [[hCard]]
* '''<code class="class-name">output</code>''':: The example output which would be expected form the test.
* '''<code class="class-name">type</code>''':: The output format
* '''<code class="class-name">value</code>''':: A URL to link to the example
* '''<code class="class-name">assert</code>''':: The assert is a description of a test
* '''<code class="class-name">test</code>''':: The element to test
* '''<code class="class-name">result</code>''':: The expected result for the test.
* '''<code class="class-name">comment</code>''':: An expanded piece of text about the test.
* '''<code class="class-name">history</code>''':: The history of changes to test-fixture, as [[hCalendar]] events

<pre><nowiki>
<h1 class="summary">hCard 1 - single occurrence test</h1>
<p class="description">
This page was designed to test the values of a hcard
which are meant to have only a single occurrence parsed correctly.
</p>

<p>From: <a href="default.htm"><span class="format">hCard</span> testsuite 1.0</a></p>

<p class="author vcard">
Author:
<a class="url fn" href="http://www.glennjones.net/">Glenn Jones</a>
<a class="org url" href="http://www.madgex.com/">Madgex</a>
</p>

<p>Output examples:
<ul>
<li class="output"><a class="url" href="hcard1.js"><span class="type">JSON</span></a></li>
<li class="output"><a class="url" href="hcard1.xml"><span class="type">XML</span></a></li>
</ul>
</p>

<p>Tests:</p>
<table id="assetTable" cellpadding="0" cellspacing="0">
<thead>
<tr>
<th>Test</th>
<th>Result</th>
<th>Comment</th>
</tr>
</thead>
<tbody>
<tr class="assert">
<td class="test">vcard[0].fn</td>
<td class="result">IsEqualTo("John Doe")</td>
<td class="comment">The fn (formatted name) is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].n.given-name[0]</td>
<td class="result">IsEqualTo("John")</td>
<td class="comment">The n (name) is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].bday</td>
<td class="result">IsEqualTo("2000-01-01T00:00:00-0800")</td>
<td class="comment">The bday (birthday) is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].class</td>
<td class="result">IsEqualTo("Public")</td>
<td class="comment">The class is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].geo.latitude</td>
<td class="result">IsEqualTo("30.267991")</td>
<td class="comment">The geo is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].rev</td>
<td class="result">IsEqualTo("2008-01-01T13:45")</td>
<td class="comment">The rev is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].role</td>
<td class="result">IsEqualTo("Designer")</td>
<td class="comment">The role is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].sort-string</td>
<td class="result">IsEqualTo("John")</td>
<td class="comment">The sort-string is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].tz</td>
<td class="result">IsEqualTo("-05:00")</td>
<td class="comment">The tz is a singular value</td>
</tr>
<tr class="assert">
<td class="test">vcard[0].uid</td>
<td class="result">IsEqualTo("com.johndoe/profiles/johndoe")</td>
<td class="comment">The uid is a singular value</td>
</tr>
</tbody>
</table>

<p>History:</p>
<ul>
<li class="history vevent">
<span class="summary">Created</span>:
<abbr class="dtstart" title="2008-04-08">8 April 2008</abbr>
<span class="description">by Glenn Jones</span>

</li>
</ul>

</div>

</nowiki></pre>

== Embeding microformats to test within the same page ==

When testing microformats you can embed them into the same page as the test-fixture. As the test-fixture itself contains microformats such as hCards so we need to define what section of the page to we should be testing. For the sake of consistency within the microformats test-suite all microformats That are been tested should be contain in a HTML element with the id “uf”.

Some parsers such as UfXtarct and Sumo already have this ability to parse only a fragement of HTML from a pgae, for other you can use a simple proxy service. It allows you to define a URL of a page and the ID of any element and it returns a HTML page containing just that element.

== Current test methods ==
* IsEqualTo()
* isEqualToCaseInsensitive()
* IsEqualToISODate()
* IsEqualToPhoneNumbers()
* isEqualToGeo()
* IsTrue()
* IsFalse()
* HasProperty()