xcfit 0.2.0

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestHttpStatus/properties.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20071130010014</LastModified>
+  <RecentChanges/>
+  <Suites></Suites>
+  <Test/>
+  <WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestImage/content.txt

@@ -0,0 +1,41 @@
+!3 This page tests the inclusion of images.
+#
+ * First create a page with a set of images in it.
+#
+|script|
+|start|Page Builder|
+|line|!-!img name-!|
+|line|!-!img-l name-!|
+|line|!-!img-r name-!|
+|line|!-!img -w 512 name-!|
+|line|!-Image should be inline !img name with the text-!|
+|line|!-!img-l -w 200 name-!|
+|line|!-!img-r -w 150 name-!|
+|line|!-!img -m 5 -b 1 name-!|
+|line|!-!img-r -w 640 -m 10 -b 2 url-!|
+|page|!-ImagePage-!|
+#
+ * Then request that page
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-ImagePage-!|true||
+#
+ * Make sure the html is correct for the images included.
+#
+|Response Examiner.|
+|type|pattern|matches?|wrapped html?|
+|contents|a|true||
+
+|Response Examiner.|
+|type|number|string?|
+|line|1|!-<img src="name"/>-!|
+|line|2|!-<img src="name" class="left"/>-!|
+|line|3|!-<img src="name" class="right"/>-!|
+|line|4|!-<img src="name" width="512"/>-!|
+|line|5|!-Image should be inline <img src="name"/> with the text-!|
+|line|6|!-<img src="name" class="left" width="200"/>-!|
+|line|7|!-<img src="name" class="right" width="150"/>-!|
+|line|8|!-<img src="name" style="border:1px solid black;margin:5px 5px 5px 5px;"/>-!|
+|line|9|!-<img src="url" class="right" width="640" style="border:2px solid black;margin:10px 10px 10px 10px;"/>-!|
+

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestImage/properties.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<RecentChanges/>
+	<Test/>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestInclude/content.txt

@@ -0,0 +1,41 @@
+!3 This page tests includes on a wiki page.
+When a !include is the first string on a line in a wiki page, then the argument of the !include is presumed to be another wiki page.  The contents of that wiki page are inserted in place of the !include.
+
+The following is a test that demonstrates how this works.
+#
+ * First create a page to be included.
+#
+|script|
+|start|Page Builder|
+|line|included|
+|page|!-IncludedPage-!|
+#
+ * Next create a page to do the including.
+#
+|script|
+|start|Page Builder|
+|line|before|
+|line|&bang;include !-IncludedPage-! |
+|line|after|
+|page|!-IncludingPage-!|
+#
+ * Then request the including page.
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-IncludingPage-!|true||
+#
+ * Examine the requested page to be sure the included page was in fact included.
+#
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|included|true||
+#
+ * Now look at every line on the including page to make sure that the inclusions were done in order.
+#
+|Response Examiner.|
+|line|occurs after?|
+|before|true|
+|included|true|
+|after|true|
+

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestInclude/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20081025203702</LastModified>
+  <Properties/>
+  <RecentChanges/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1224985022046</saveId>
+  <ticketId>-1624419353663413223</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeBackwardsSearchPage/content.txt

@@ -0,0 +1,33 @@
+!3 This page tests includes of a backwards search page.
+
+Make sure the !-!include <MyAncestorPage.MyPage-! syntax works.
+#
+ * First create a page to be included.
+#
+|script|
+|start|Page Builder|
+|line|this subpage was included 3.14159|
+|page|!-ParentPage.MiddlePage.IncludedPage-!|
+#
+ * Next create a page to do the including.
+#
+|script|
+|start|Page Builder|
+|line|before|
+|line|!-&bang;include <MiddlePage.IncludedPage
+-! |
+|line|after|
+|page|!-ParentPage.MiddlePage.MiddlePageTwo.IncludingPage-!|
+#
+ * Then request the including page.
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-ParentPage.MiddlePage.MiddlePageTwo.IncludingPage-!|true||
+#
+ * Examine the requested page to be sure the included page was in fact included.
+#
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|this subpage was included 3.14159|true||
+#

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeBackwardsSearchPage/properties.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<Test/>
+<WhereUsed/>
+<saveId>1224985098949</saveId>
+<ticketId>1988325188839757829</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeCollapsed/content.txt

@@ -0,0 +1,36 @@
+!3 You can set an included page to be collapsed when the page is rendered.
+To do this, add the option "-c":
+
+!-!include -c SomePage-!
+
+See TestInclude for more info on included pages.
+----
+#
+ * First create a page to be included.
+#
+|script|
+|start|Page Builder|
+|line|included|
+|page|!-IncludedPage-!|
+#
+ * Next create a page to do the including.
+#
+|script|
+|start|Page Builder|
+|line|before|
+|line|!-&bang;include -c IncludedPage-! |
+|line|after|
+|page|!-IncludingPage-!|
+#
+ * Then request the including page.
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-IncludingPage-!|true||
+#
+ * Now make sure the page was included and that the correct style and image are used.
+#
+|Response Examiner.|
+|type|pattern|matches?|
+|contents|included|true|
+|contents|class="collapsible closed"|true|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeCollapsed/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<Help></Help>
+	<RecentChanges/>
+	<Suites/>
+	<Test/>
+	<WhereUsed/>
+	<saveId>1224985151218</saveId>
+	<ticketId>1162019334740908922</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeIsCollapsable/content.txt

@@ -0,0 +1,32 @@
+!3 Included Pages are Collapsable
+When a page is included it is included within a division that is collapsable.
+
+The following is a test that demonstrates how this works.
+#
+ * First create a page to be included.
+#
+|script|
+|start|Page Builder|
+|line|included|
+|page|!-IncludedPage-!|
+#
+ * Next create a page to do the including.
+#
+|script|
+|start|Page Builder|
+|line|before|
+|line|!-&bang;include IncludedPage-! |
+|line|after|
+|page|!-IncludingPage-!|
+#
+ * Then request the including page.
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-IncludingPage-!|true||
+#
+ * Examine the requested page to be sure the included page was in fact included.
+#
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|class="collapsible"|true||

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeIsCollapsable/properties.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<Help></Help>
+	<RecentChanges/>
+	<Test/>
+	<WhereUsed/>
+	<saveId>1224985202193</saveId>
+	<ticketId>-5717088232592493606</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeSeamless/content.txt

@@ -0,0 +1,45 @@
+!3 This page tests seamless includes on a wiki page.
+
+'''NOTE - this is not part of the 20050301 release, but is checked in and will be part of the next release'''
+
+You can follow !include (see TestInclude) with the option "!--seamless-!", which renders the included comment with no additional decoration.
+
+The following is a test that demonstrates how this works.
+#
+ * First create a page to be included.
+#
+|script|
+|start|Page Builder|
+|line|included line 1|
+|line|included line 2|
+|page|!-IncludedPage-!|
+#
+ * Next create a page to do the including.
+#
+|script|
+|start|Page Builder|
+|line|before|
+|line|!-&bang;include -seamless IncludedPage-! |
+|line|after|
+|page|!-IncludingPage-!|
+#
+ * Then request the including page.
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-IncludingPage-!|true||
+#
+ * Examine the requested page to be sure the included page was in fact included.
+#
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|included|true||
+#
+ * Now look at every line on the including page to make sure that the inclusions were done in order.
+#
+|Response Examiner.|
+|type|number|string?|
+|line|1|before|
+|line|2|included line 1|
+|line|3|included line 2|
+|line|4|after|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeSeamless/properties.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20081025204051</LastModified>
+  <RecentChanges/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1224985251533</saveId>
+  <ticketId>6002595183983437420</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeSetUpTearDownWithPageName/content.txt

@@ -0,0 +1,17 @@
+!*< test page content definition
+!define pageContent (!include -setup SetUp
+!include IncludedPage
+Including page name is !-${PAGE_NAME}-!
+!include -teardown TearDown)
+
+*!
+
+!|script|
+|create page|SetUp|with content|Set Up page name is !-${PAGE_NAME}-!|
+|create page|TearDown|with content|Tear Down page name is !-${PAGE_NAME}-!|
+|create page|IncludedPage|with content|Included page name is !-${PAGE_NAME}-!|
+|given page|IncludingPage|with content|${pageContent}|
+|it should contain|Included page name is <a href="IncludedPage">IncludedPage|
+|it should contain|Including page name is <a href="IncludingPage">IncludingPage|
+|it should contain|Set Up page name is <a href="IncludingPage">IncludingPage|
+|it should contain|Tear Down page name is <a href="IncludingPage">IncludingPage|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeSetUpTearDownWithPageName/properties.xml

@@ -0,0 +1,15 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit>true</Edit>
+	<Files>true</Files>
+	<LastModified>20090319152813</LastModified>
+	<Properties>true</Properties>
+	<RecentChanges>true</RecentChanges>
+	<Refactor>true</Refactor>
+	<Search>true</Search>
+	<Test>true</Test>
+	<Versions>true</Versions>
+	<WhereUsed>true</WhereUsed>
+	<saveId>1237470268676</saveId>
+	<ticketId>-6178655714902395693</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeSubPage/content.txt

@@ -0,0 +1,32 @@
+!3 This page tests includes of a sub page.
+
+Make sure the !-!include >MySubPage-! syntax works.
+#
+ * First create a page to be included.
+#
+|script|
+|start|Page Builder|
+|line|this subpage was included 3.14159|
+|page|!-IncludingPage.IncludedPage-!|
+#
+ * Next create a page to do the including.
+#
+|script|
+|start|Page Builder|
+|line|before|
+|line|!-&bang;include >IncludedPage-! |
+|line|after|
+|page|!-IncludingPage-!|
+#
+ * Then request the including page.
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-IncludingPage-!|true||
+#
+ * Examine the requested page to be sure the included page was in fact included.
+#
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|this subpage was included 3.14159|true||
+#

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestIncludeSubPage/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20081025204138</LastModified>
+  <RecentChanges/>
+  <Suites/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1224985298639</saveId>
+  <ticketId>-7592481394649690785</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestLineBreak/content.txt

@@ -0,0 +1,30 @@
+!3 This page tests line breaks.
+#
+ * First create a page with line breaks in it.
+#
+|script|
+|start|Page Builder|
+|line|one|
+|line||
+|line|two|
+|page|!-LineBreakPage-!|
+#
+ * Then request that page
+#
+|Response Requester.|
+|uri|valid?|contents?|
+|!-LineBreakPage-!|true||
+#
+ * Make sure the page has three line breaks.
+#
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|one.*<br/>.*<br/>.*two.*<br/>.*|true||
+
+
+
+
+
+
+
+

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestLineBreak/properties.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20081026072729</LastModified>
+  <RecentChanges/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1225024049237</saveId>
+  <ticketId>-7002969980886143726</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteWidgetTests/TestLinkAlias/content.txt

@@ -0,0 +1,143 @@
+!2 Test the Link Alias syntax.
+Aliases to links can be created using the !-[[tag][link]]-! syntax.
+The tag is interpreted for markup syntax, so it can be italic, or bold, or an image, etc.  The link can be a relative or global wiki word, or it can be an http link.
+
+----
+!3 Test relative link alias
+ * First create two sub pages.  One has a relative link to the other.
+|Page creator.|
+|Page name.|Page contents.|Page attributes.|valid?|
+|!-SomePage.TargetPage-!|target page||true|
+|!-SomePage.LinkPage-!|!-[[tag][TargetPage]]-!||true|
+ * Then get the page with the relative link on it.
+|Response Requester.|
+|uri|valid?|
+|!-SomePage.LinkPage-!|true|
+ * Then make sure the relative link is properly constructed.
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|<a href=!-"SomePage.TargetPage"-!>tag</a>|true||
+----
+!3 Test global link alias
+ * First create a sub page that has a global reference to another sub page.
+|Page creator.|
+|Page name.|Page contents.|Page attributes.|valid?|
+|!-SomePage.GlobalLinkPage-!|!-[[tag][.SomePage.TargetPage]]-!||true|
+ * Then fetch that page.
+|Response Requester.|
+|uri|valid?|
+|!-SomePage.GlobalLinkPage-!|true|
+ * Make sure the link is properly formed.
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|<a href=!-"SomePage.TargetPage"-!>tag</a>|true||
+----
+!3 Test variables get rendered in http link alias
+ * First create a page with a variable and http link on it.
+!|script|
+|start|Page Builder|
+|line|&bang;define HOST {localhost:8080}|
+|line|!-[[tag][http://${HOST}/page]]-! works fine.|
+|page|!-HttpLinkPage-!|
+
+ * Fetch the page.
+|Response Requester.|
+|uri|valid?|
+|!-HttpLinkPage-!|true|
+ * Make sure the link is properly constructed.
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|<a href=!-"http://localhost:8080/page"-!>tag</a> works fine.|true||
+----
+!3 Test variables defined in parent page get rendered in http link alias on child pages
+ * First define parent page with variable definition and child page with a http link which uses the variable.
+|Page creator.|
+|Page name.|Page contents.|Page attributes.|valid?|
+|!-SomePage.ParentPage-!|!-!define HOST {localhost:8080}-!||true|
+|!-SomePage.ParentPage.ChildPage-!|!-[[tag][http://${HOST}/page]]-! works fine.||true|
+
+ * Fetch the page.
+|Response Requester.|
+|uri|valid?|
+|!-SomePage.ParentPage.ChildPage-!|true|
+
+ * Make sure the link is properly constructed.
+|Response Examiner.|
+|type|pattern|matches?|value|
+|contents|<a href=!-"http://localhost:8080/page"-!>tag</a> works fine.|true||
+-----
+!3 Test expressions without variables in link alias
+ * Create pages to refer to
+|Page creator.|
+|Page name.|Page contents.|Page attributes.|valid?|
+|!-PageLink2-!|contents||true|
+|!-PageLink4-!|contents||true|
+|!-PageLink10-!|contents||true|
+
+ * First create a page with a variables and http link on it.
+|script|
+|start|Page Builder|
+|line|!-!define X {5}-!|
+|line|!-!define Y (4)-!|
+|line|!-!define EXPR (${=3+2-1=})-!|
+|line|!-[[tag][PageLink${= 3 - 2 + 1 =}]]-! works fine.|
+|line|!-[[tag][PageLink${EXPR}]]-! works too.|
+|line|!-[[tag][PageLink${=${X}+${Y}+1=}]]-! works as well.|
+|page|!-HttpExprPage-!|
+
+ * Fetch the page.
+|Response Requester.|
+|uri|valid?|contents?|
+|!-HttpExprPage-!|true||
+
+ * Make sure the link is properly constructed.
+|Response Examiner.|
+|type|pattern|matches?|
+|contents|<a href=!-"PageLink2"-!>tag</a> works fine.|true|
+|contents|<a href=!-"PageLink4"-!>tag</a> works too.|true|
+|contents|<a href=!-"PageLink10"-!>tag</a> works as well.|true|
+
+!3 Test that links with query strings and fragments are handled properly.
+ * Create a page hierarchy
+|Page creator.|
+|Page name.|Page contents.|Page attributes.|valid?|
+|!-QueryPageRoot-!                  |!-!anchor QPLabel   -!||true|
+|!-QueryPageRoot.TopPage-!          |!-!anchor QPTopLabel-!||true|
+
+ * Create a page of query and fragment links...and a child
+|script|
+|start|Page Builder|
+|line|!-[[tag1 ][TopPage?edit]]-! has query.|
+|line|!-[[tag2 ][TopPage?edit#QPTopLabel]]-! has query and frag.|
+|line|!-[[tag3 ][TopPage#QPTopLabel]]-! has fragment.|
+|line|!-[[tag4 ][<QueryPageRoot.TopPage?edit]]-! back has query.|
+|line|!-[[tag5 ][.QueryPageRoot.TopPage?edit]]-! root has query.|
+|line|!-[[tag6 ][<QueryPageRoot.TopPage?edit#QPTopLabel]]-! back has query and frag.|
+|line|!-[[tag7 ][<QueryPageRoot.TopPage#QPTopLabel]]-! back has fragment.|
+|line|!-[[tag8 ][>ChildFrag?edit]]-! child has query.|
+|line|!-[[tag9 ][>ChildFrag?edit#QPTopLabel]]-! child has query and frag.|
+|line|!-[[tag10][>ChildFrag#QPTopLabel]]-! child has fragment.|
+|page|!-QueryPageRoot.QueryFragmentLinks-!|
+
+|Page creator.|
+|Page name.|Page contents.|Page attributes.|valid?|
+|!-QueryPageRoot.QueryFragmentLinks.ChildFrag-!|!-!anchor QPChild-!||true|
+
+ * Fetch the page.
+|Response Requester.|
+|uri|valid?|contents?|
+|!-QueryPageRoot.QueryFragmentLinks-!|true||
+
+ * Make sure the query and fragments don't interfere with page paths.
+|Response Examiner.|
+|type|pattern|matches?|
+|contents|<a href=!-"QueryPageRoot\.TopPage\?edit"-!>tag1 </a> has query.|true|
+|contents|<a href=!-"QueryPageRoot\.TopPage\?edit#QPTopLabel"-!>tag2 </a> has query and frag.|true|
+|contents|<a href=!-"QueryPageRoot\.TopPage#QPTopLabel"-!>tag3 </a> has fragment.|true|
+|contents|<a href=!-"QueryPageRoot\.TopPage\?edit"-!>tag4 </a> back has query.|true|
+|contents|<a href=!-"QueryPageRoot\.TopPage\?edit"-!>tag5 </a> root has query.|true|
+|contents|<a href=!-"QueryPageRoot\.TopPage\?edit#QPTopLabel"-!>tag6 </a> back has query and frag.|true|
+|contents|<a href=!-"QueryPageRoot\.TopPage#QPTopLabel"-!>tag7 </a> back has fragment.|true|
+|contents|<a href=!-"QueryPageRoot\.QueryFragmentLinks\.ChildFrag\?edit"-!>tag8 </a> child has query.|true|
+|contents|<a href=!-"QueryPageRoot\.QueryFragmentLinks\.ChildFrag\?edit#QPTopLabel"-!>tag9 </a> child has query and frag.|true|
+|contents|<a href=!-"QueryPageRoot\.QueryFragmentLinks\.ChildFrag#QPTopLabel"-!>tag10</a> child has fragment.|true|