value-class-pattern-tests - Revision history

GRegorLove: s///

2023-07-26T21:40:27Z

s/<source>/<syntaxhighlight>/

← Older revision		Revision as of 21:40, 26 July 2023
Line 40:		Line 40:
	====One====		====One====

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<p class='tel'>My		<p class='tel'>My
	<span class='type'>		<span class='type'>
Line 46:		Line 46:
	</span> phone number is <span class='value'>+44 1245 333 333</span>		</span> phone number is <span class='value'>+44 1245 333 333</span>
	</p>		</p>
	</~~source~~>		</syntaxhighlight>

	Result		Result

	<~~source lang=text~~>		<pre>
	TEL		TEL
	TYPE = cell		TYPE = cell
	VALUE = +44 1245 333 333		VALUE = +44 1245 333 333
	</~~source~~>		</pre>

	====Two====		====Two====

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<p class='vevent'>		<p class='vevent'>
	My <span class='summary'>Birthday Party</span> will be held		My <span class='summary'>Birthday Party</span> will be held
Line 70:		Line 70:
	</span>.		</span>.
	</p>		</p>
	</~~source~~>		</syntaxhighlight>

	Result		Result

	<~~source lang=text~~>		<pre>
	VEVENT		VEVENT
	SUMMARY = Birthday Party		SUMMARY = Birthday Party
	DTSTART = 2009-04-01		DTSTART = 2009-04-01
	DTEND = 2009-04-05		DTEND = 2009-04-05
	</~~source~~>		</pre>

	===Tests of Non-Conforming <code>value-title</code> Code===		===Tests of Non-Conforming <code>value-title</code> Code===
Line 87:		Line 87:
	In this case, the human text appears before the <code>value-title</code> element, so the machine-data value has a weaker association with the property declaration. The likelihood of the data not being maintained correctly — the data value being ignored by an editor — is increased.		In this case, the human text appears before the <code>value-title</code> element, so the machine-data value has a weaker association with the property declaration. The likelihood of the data not being maintained correctly — the data value being ignored by an editor — is increased.

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<p class='tel'>My		<p class='tel'>My
	<span class='type'>		<span class='type'>
Line 94:		Line 94:
	</span> phone number is <span class='value'>+44 1245 333 333</span>		</span> phone number is <span class='value'>+44 1245 333 333</span>
	</p>		</p>
	</~~source~~>		</syntaxhighlight>

	Result		Result

	<~~source lang=text~~>		<pre>
	TEL		TEL
	TYPE = none/default/unknown ('mobile' is unknown in hCard)		TYPE = none/default/unknown ('mobile' is unknown in hCard)
	VALUE = +44 1245 333 333		VALUE = +44 1245 333 333
	</~~source~~>		</pre>

	====Two====		====Two====
Line 108:		Line 108:
	In this case, the <code>value-title</code> element is used for a property that is not valid for use with this pattern.		In this case, the <code>value-title</code> element is used for a property that is not valid for use with this pattern.

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<p class='vevent'>You are invited to		<p class='vevent'>You are invited to
	<span class='summary'>		<span class='summary'>
Line 115:		Line 115:
	</span>		</span>
	</p>		</p>
	</~~source~~>		</syntaxhighlight>

	Result		Result

	<~~source lang=text~~>		<pre>
	VEVENT		VEVENT
	SUMMARY = BarCamp		SUMMARY = BarCamp
	</~~source~~>		</pre>

	== inline examples from Microformation ==		== inline examples from Microformation ==
Line 139:		Line 139:

	=== value title with contents ===		=== value title with contents ===
	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<span class="dtstart">		<span class="dtstart">
	<span class="value-title" title="2009-06-05T20:00:00">		<span class="value-title" title="2009-06-05T20:00:00">
Line 145:		Line 145:
	</span>		</span>
	</span>		</span>
	</~~source~~>		</syntaxhighlight>

	=== separate value title date and time ===		=== separate value title date and time ===
	Not sure if this is actually allowed by the [[value-class-pattern]], but we should write up a test case regardless, to see what implementations do. [[User:Tantek\|Tantek]]		Not sure if this is actually allowed by the [[value-class-pattern]], but we should write up a test case regardless, to see what implementations do. [[User:Tantek\|Tantek]]

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<span class="dtstart">		<span class="dtstart">
	<span class="value-title" title="2009-06-05">		<span class="value-title" title="2009-06-05">
Line 160:		Line 160:
	</span>		</span>
	</span>		</span>
	</~~source~~>		</syntaxhighlight>

	=== value title span with empty content ===		=== value title span with empty content ===
	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<span class="dtstart">		<span class="dtstart">
	<span class="value-title" title="2009-06-05T20:00:00"> </span>		<span class="value-title" title="2009-06-05T20:00:00"> </span>
	Friday, June 5th at 8pm		Friday, June 5th at 8pm
	</span>		</span>
	</~~source~~>		</syntaxhighlight>

	== see also ==		== see also ==

Tantek: /* inline examples from Microformation */ to do value-title test pages

2012-11-16T19:21:02Z

inline examples from Microformation: to do value-title test pages

← Older revision		Revision as of 19:21, 16 November 2012
Line 125:		Line 125:

	== inline examples from Microformation ==		== inline examples from Microformation ==
	Here are inline examples published by Jeremy Keith in his blog post [http://adactio.com/journal/1579/ Microformation]. Each of ~~these~~ examples needs to be updated as follows:		Here are inline examples published by Jeremy Keith in his blog post [http://adactio.com/journal/1579/ Microformation].

			=== to do value-title test pages ===
			'''Each of the examples below needs to be updated as follows:'''

	# move to a separate page (one test per page), similar to the format used by [[value-dt-test-YYYY-MM-DD--HH-MM]].		# move to a separate page (one test per page), similar to the format used by [[value-dt-test-YYYY-MM-DD--HH-MM]].
Line 133:		Line 136:
	# linked to from the appropriate section at the top of this page.		# linked to from the appropriate section at the top of this page.

	Please help the value class pattern testing, development, and implementation effort by creating test ~~cases from~~ the following examples:		Please help the value class pattern testing, development, and implementation effort by creating separate test case pages for each of the following examples.

	=== value title with contents ===		=== value title with contents ===
Line 166:		Line 169:
	</span>		</span>
	</source>		</source>


	== see also ==		== see also ==

Tantek: /* Two */ add close p tag

2010-03-16T02:00:05Z

Two: add close p tag

← Older revision		Revision as of 02:00, 16 March 2010
Line 114:		Line 114:
	BarCamp		BarCamp
	</span>		</span>
			</p>
	</source>		</source>

Tantek: /* Date and time values */ added direct links to all value class pattern date and time test cases

2009-10-06T15:51:08Z

Date and time values: added direct links to all value class pattern date and time test cases

@@ Line 9: / Line 9: @@
 * [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]]
 * [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]]
-* ...
+* [[value-dt-test-YYYY-MM-DD--HHpm]]
 === Parsing value from a title attribute ===

Tantek: add value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM and add more examples from Jeremy Keith's blog post microformation

2009-07-07T01:36:22Z

add value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM and add more examples from Jeremy Keith's blog post microformation

@@ Line 8: / Line 8: @@
 * [[value-dt-test-YYYY-MM-DD--HH-MM]]
 * [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]]
 * ...
@@ Line 13: / Line 14: @@
 * ...
-== inline tests ==
+== inline development tests ==
 Here are inline tests developed during the development and design of the [[value-class-pattern]]. Each of those tests needs to be updated as follows:
@@ Line 109: / Line 110: @@
      SUMMARY = BarCamp
 </source>
 == see also ==

Tantek: added newly created value class pattern date and time value tests, conversion notes from a collection of inline tests to individual test pages marked up with test-fixture

2009-07-07T00:04:45Z

added newly created value class pattern date and time value tests, conversion notes from a collection of inline tests to individual test pages marked up with test-fixture

← Older revision		Revision as of 00:04, 7 July 2009
Line 1:		Line 1:
	~~We require~~ a thorough test-suite for the [[value-class-pattern]]~~, but in the interim~~, here ~~is an incomplete~~ test ~~suite~~:		With the goal of developing a thorough test-suite for the [[value-class-pattern]], here are some test cases:

	==~~Conforming <code>~~value-~~title</code> Tests==~~		== test cases ==
			The following value-class-pattern test cases have been developed (all of which use the [[test-fixture]] poshformat for easier extraction).

	===One===		=== Date and time values ===
			{{main\|value-class-date-time-tests}}
			* [[value-dt-test-YYYY-MM-DD--HH-MM]]
			* [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]]
			* ...

			=== Parsing value from a title attribute ===
			* ...

			== inline tests ==
			Here are inline tests developed during the development and design of the [[value-class-pattern]]. Each of those tests needs to be updated as follows:

			# move to a separate page (one test per page), similar to the format used by [[value-dt-test-YYYY-MM-DD--HH-MM]].
			# mark up using the [[test-fixture]] poshformat.
			# "Result" at a minimum converted from abstract hierarchical text properties/values to an [[vCard]] and/or [[iCalendar]] expected result block.
			# linked to from the previous section.

			Please help the value class pattern testing, development, and implementation effort by updating the following tests accordingly:

			===Conforming <code>value-title</code> Tests===

			====One====

	<source lang=html4strict>		<source lang=html4strict>
Line 21:		Line 43:
	</source>		</source>

	===Two===		====Two====

	<source lang=html4strict>		<source lang=html4strict>
Line 46:		Line 68:
	</source>		</source>

	==Tests of Non-Conforming <code>value-title</code> Code==		===Tests of Non-Conforming <code>value-title</code> Code===

	===One===		====One====

	In this case, the human text appears before the <code>value-title</code> element, so the machine-data value has a weaker association with the property declaration. The likelihood of the data not being maintained correctly — the data value being ignored by an editor — is increased.		In this case, the human text appears before the <code>value-title</code> element, so the machine-data value has a weaker association with the property declaration. The likelihood of the data not being maintained correctly — the data value being ignored by an editor — is increased.
Line 69:		Line 91:
	</source>		</source>

	===Two===		====Two====

	In this case, the <code>value-title</code> element is used for a property that is not valid for use with this pattern.		In this case, the <code>value-title</code> element is used for a property that is not valid for use with this pattern.
Line 87:		Line 109:
	SUMMARY = BarCamp		SUMMARY = BarCamp
	</source>		</source>

			== see also ==
			* [[value-class-pattern]]
			* [[value-class-date-time-tests]]
			* [[test-fixture]]

BenWard: Break test cases out into separate page

2009-04-17T05:44:14Z

Break test cases out into separate page

New page

We require a thorough test-suite for the [[value-class-pattern]], but in the interim, here is an incomplete test suite:

==Conforming <code>value-title</code> Tests==

===One===

<source lang=html4strict>
My

 mobile
 phone number is +44 1245 333 333

</source>

Result

<source lang=text>
TEL
TYPE = cell
VALUE = +44 1245 333 333
</source>

===Two===

<source lang=html4strict>

My Birthday Party will be held

tomorrow

and last until

 
the following Tuesday (April 5th)
.

</source>

Result

<source lang=text>
VEVENT
SUMMARY = Birthday Party
DTSTART = 2009-04-01
DTEND = 2009-04-05
</source>

==Tests of Non-Conforming <code>value-title</code> Code==

===One===

In this case, the human text appears before the <code>value-title</code> element, so the machine-data value has a weaker association with the property declaration. The likelihood of the data not being maintained correctly — the data value being ignored by an editor — is increased.

<source lang=html4strict>
My

mobile
 
 phone number is +44 1245 333 333

</source>

Result

<source lang=text>
TEL
TYPE = none/default/unknown ('mobile' is unknown in hCard)
VALUE = +44 1245 333 333
</source>

===Two===

In this case, the <code>value-title</code> element is used for a property that is not valid for use with this pattern.

<source lang=html4strict>
You are invited to

 
BarCamp

</source>

Result

<source lang=text>
VEVENT
SUMMARY = BarCamp
</source>