xcfit 0.2.0

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameInProperties/content.txt

@@ -0,0 +1,10 @@
+The username of the person who last modified a page is displayed in the properties view of the modified page.
+
+!|script|
+|save page|PageOne|by user|Aladdin|
+|it's last modified by should be|Aladdin|
+|save page|PageTwo|by user|Genie|
+|it's last modified by should be|Genie|
+|save page|PageThree|
+|it's last modified by should be|null|
+

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameInProperties/properties.xml

@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help/>
+	<Properties/>
+	<RecentChanges/>
+	<Refactor/>
+	<Search/>
+	<Suites/>
+	<Test/>
+	<Versions/>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameInRecentChanges/content.txt

@@ -0,0 +1,6 @@
+!-RecentChanges-! displays the username of the last user that modified each page.  If the user is anonymous then it is not displayed.
+
+!|script|
+|page|RecentChanges|should not contain|Aladdin|
+|save page|SomePage|by user|Aladdin|
+|page|RecentChanges|should contain|Aladdin|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameInRecentChanges/properties.xml

@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help/>
+	<Properties/>
+	<RecentChanges/>
+	<Refactor/>
+	<Search/>
+	<Suites/>
+	<Test/>
+	<Versions/>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameInVersions/content.txt

@@ -0,0 +1,7 @@
+When viewing versions, the user who created each ''previous'' version is listed along with each version.  Anonymous users are omitted.
+
+!|script|
+|save page|MyPage|by user|Bob|
+|save page|MyPage|by user|Bill|
+|it's versions should contain|Bob|
+|and should match|>\d+<|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameInVersions/properties.xml

@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help/>
+	<Properties/>
+	<RecentChanges/>
+	<Refactor/>
+	<Search/>
+	<Suites/>
+	<Test/>
+	<Versions/>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameSaved/content.txt

@@ -0,0 +1,7 @@
+The username is saved when a page is edited.  It is visible through use of the !-!lastmodified-! widget.
+
+!|script|
+|save page|MyPage|with contents|!lastModified|
+|it should not contain|bob|
+|save page|MyPage|with contents|!lastmodified|by user|bob|
+|it should contain|bob|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/TestUserNameSaved/properties.xml

@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help/>
+	<Properties/>
+	<RecentChanges/>
+	<Refactor/>
+	<Search/>
+	<Suites/>
+	<Test/>
+	<Versions/>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/content.txt

@@ -0,0 +1,3 @@
+The edit responder is invoked with a url of the form {{{SomePage?edit}}}
+!contents -R2 -p
+!define TEST_SYSTEM {slim}

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteEditResponderTests/properties.xml

@@ -0,0 +1,16 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help/>
+	<Properties/>
+	<RecentChanges/>
+	<Refactor/>
+	<Search/>
+	<Suite/>
+	<Suites/>
+	<Versions/>
+	<WhereUsed/>
+	<saveId>1229153668185</saveId>
+	<ticketId>5760355884637638070</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/CopyAndAppendLastRow/content.txt

@@ -0,0 +1,12 @@
+There are cases when you want to copy and append the last row of your column or row fixture certain number of times.
+
+For Ex: We make a query to the database and it return certain record 'n' number of times. Instead of writing the same record 'n' number of times in your fitnesse page, you can just specify that you expect the last column 'n' number of times using the !-CopyAndAppendLastRow-! decorator.
+
+!|Copy and Append Last Row|100|number of times|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|12.6|3|4.2|
+|100|4|25|
+
+In the above example, we want to divide 100 by 4 101 times.

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/CopyAndAppendLastRow/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+  <Edit/>
+  <Files/>
+  <LastModified>20061216213113</LastModified>
+  <Properties/>
+  <RecentChanges/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1166322673244</saveId>
+  <secure-write/>
+  <ticketId>524008525574625139</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/CopyAppendLastRowAndIncrementColumnValues/content.txt

@@ -0,0 +1,12 @@
+What if you want to call the fixture 'n' times with the same row except you want to update one or two column's value?
+
+Ex: If you are using fitnesse fixtures to populate database and you want to insert a record 500 times. It would be easy to write one model record and insert that 500 times. This can be easily done with the !-CopyAndAppendLastRow-! decorator. But the database table might have a primary key. So you might want to update the primary key in each row. Now you might want to pipe !-IncrementColumnsValue-! and !-CopyAndAppendLastRow-! decorators to get the job done.
+
+Here is an example where I want to divide 5 by 1, 100 times, but I also want to update the numerator by 5 and denominator by 1.
+
+!|Copy and Append Last Row|100|times|
+|Increment Columns Value|numerator|of type|int|by|5|
+|Increment Columns Value|denominator|of type|int|by|1|
+|Division|
+|numerator|denominator|quotient()|
+|5|1|5|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/CopyAppendLastRowAndIncrementColumnValues/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+  <Edit/>
+  <Files/>
+  <LastModified>20061216215829</LastModified>
+  <Properties/>
+  <RecentChanges/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1166324308994</saveId>
+  <secure-write/>
+  <ticketId>-8528063939302055872</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/IncrementColumnsValues/content.txt

@@ -0,0 +1,42 @@
+What if you want to increment the value of one of the columns of your fixture table at run time? You can use the !-IncrementColumnsValue-! decorator. This lets you increment column's values. This decorator supports the following data types:
+ * int or integer
+ * double
+ * string
+ * date
+
+!|Increment Columns Value|numerator|of type|int|by|5|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|10|3|5|
+|10|4|5|
+
+!|Increment Columns Value|numerator|of type|integer|by|5|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|10|3|5|
+|10|4|5|
+
+!|Increment Columns Value|numerator|of type|double|by|10.2|
+|Division|
+|numerator|denominator|quotient()|
+|10.2|2|5.1|
+|10.2|4|5.1|
+
+!|Increment Columns Value|numerator|of type|string|by|5|
+|Division|
+|numerator|denominator|quotient()|
+|5|1|5|
+|5|11|5|
+|5|111|5|
+
+Updates the dates by 5 days.
+!|Increment Columns Value|inDate|of type|date|by|5|
+|Get Dates|
+|inDate|updatedDate()|
+|12/02/2006|12/02/2006|
+|12/02/2006|12/07/2006|
+|12/22/2006|01/01/2007|
+
+This decorator by itself is not as useful. But piped with other decorators this can be really handy.

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/IncrementColumnsValues/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+  <Edit/>
+  <Files/>
+  <LastModified>20081020135129</LastModified>
+  <Properties/>
+  <RecentChanges/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1166413276084</saveId>
+  <secure-write/>
+  <ticketId>8229942939854899838</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/MaxTimeDivision/content.txt

@@ -0,0 +1,20 @@
+Consider you have a simple fit test as follows:
+
+!|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|12.6|3|4.2|
+|100|4|25|
+
+Now you want to measure how much time this test is taking to execute. But you don't want to or cannot modify the existing test fixture. Basically you want to decorate the existing fit tests with extra features.
+
+It would be cool if you could write a decorator around your fit test which starts a timer before the execution of the fit test starts, runs the fit test as usual and once the execution is completed it records the amount of time it took to run the test. An assertion on the execution time to make sure it executes within a max time is also quite handy to be aware of the application's performance over a period of time. Something like this:
+
+!|Max Time|100|milliseconds|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|12.6|3|4.2|
+|100|4|25|
+
+'''Note:''' As of now, all the times are in milliseconds. The parameter "milliseconds" in the fixture above is just ignored.

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/MaxTimeDivision/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+  <Edit/>
+  <Files/>
+  <LastModified>20081020135129</LastModified>
+  <Properties/>
+  <RecentChanges/>
+  <Test/>
+  <WhereUsed/>
+  <saveId>1166312743925</saveId>
+  <secure-write/>
+  <ticketId>-1637353253013255969</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/MultipleDivision/content.txt

@@ -0,0 +1,15 @@
+What if you want to execute the same fitnesse test multiple times. This seems like nice a candidate for a decorator.
+
+If you want to loop 5 times over a fitnesse table and make sure each time the test does not take more than 1000 milliseconds.
+
+!|Loop|5|times|
+|Max Time|1000|milliseconds|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|12.6|3|4.2|
+|100|4|25|
+
+Once you run this test, you can see actual time taken for each run. In our case, we'll see 5 actual timing printed, since we are looping 5 times.
+
+'''Note:''' As you can see, you can pipe decorators. Similar to how you can pipe Unix shell commands.

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/MultipleDivision/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help></Help>
+	<Properties/>
+	<RecentChanges/>
+	<Test/>
+	<WhereUsed/>
+	<saveId>1166313289708</saveId>
+	<secure-write/>
+	<ticketId>-7438421477570336896</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/SetUp/content.txt

@@ -0,0 +1,4 @@
+!|Import|
+|fit.decorator|
+|fit.decorator.performance|
+|eg|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/SetUp/properties.xml

@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<properties>
+  <Edit>true</Edit>
+  <Files>true</Files>
+  <LastModified>20061216183948</LastModified>
+  <Properties>true</Properties>
+  <RecentChanges>true</RecentChanges>
+  <Refactor>true</Refactor>
+  <Search>true</Search>
+  <Versions>true</Versions>
+  <WhereUsed>true</WhereUsed>
+  <saveId>1166312388007</saveId>
+  <ticketId>-6757238585913794424</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/TearDown/content.txt

@@ -0,0 +1 @@
+!|fit.Summary|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/TearDown/properties.xml

@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<properties>
+  <Edit>true</Edit>
+  <Files>true</Files>
+  <LastModified>20061216141632</LastModified>
+  <Properties>true</Properties>
+  <RecentChanges>true</RecentChanges>
+  <Refactor>true</Refactor>
+  <Search>true</Search>
+  <Versions>true</Versions>
+  <WhereUsed>true</WhereUsed>
+  <saveId>1166296592283</saveId>
+  <ticketId>-5128325404176707243</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/TimeRangeDivision/content.txt

@@ -0,0 +1,19 @@
+What if you want to specify a time range for your fitnesse fixtures?
+
+!|Time Range|0|milliseconds min and max|200|milliseconds|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|12.6|3|4.2|
+|100|4|25|
+
+In this example, you want to make sure all the division don't take less than 0 milliseconds and more than 50 milliseconds.
+
+By now you should be aware that these decorators ignore alternative column names.
+
+!|Time Range|0|alternative column values are ignored|200|this is ignored as well|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|12.6|3|4.2|
+|100|4|25|

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/TimeRangeDivision/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help></Help>
+	<Properties/>
+	<RecentChanges/>
+	<Test/>
+	<WhereUsed/>
+	<saveId>1166313795208</saveId>
+	<secure-write/>
+	<ticketId>-6211985429310204450</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/TimedMultipleDivision/content.txt

@@ -0,0 +1,12 @@
+What if you want to run the same fitnesse fixture, 5 times and want to make sure that each time it runs it does not take more than 200 milliseconds? Also you want to make sure overall, it does not take more than 1000 milliseconds.
+
+!|Max Time|1000|milliseconds|
+|Loop|5|times|
+|Max Time|200|milliseconds|
+|Division|
+|numerator|denominator|quotient()|
+|10|2|5|
+|12.6|3|4.2|
+|100|4|25|
+
+'''Note:''' Again you can see here, how you can pipe different decorators and create powerful decorator patterns.

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/TimedMultipleDivision/properties.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Help></Help>
+	<Properties/>
+	<RecentChanges/>
+	<Test/>
+	<WhereUsed/>
+	<saveId>1166313499121</saveId>
+	<secure-write/>
+	<ticketId>8781183260268546089</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/content.txt

@@ -0,0 +1,17 @@
+!-FitDecorator-! is a framework for writing decorator for FIT fixtures. !-FitDecorator-! help you to add new functionality to existing fixture classes without having to update them. You can just decorate the table on the fitnesse page with the appropriate !-FitDecorator-!.
+
+For example, if you want to approximately know how much time each fixture is taking during a fitnesse test, you can decorate the existing fitnesse table with a !-MaxTime-! decorator.
+
+List of available decorators and their functionality with an example:
+
+ * [[Measure Max Time taken by the Division Fixture by using !-MaxTime-! decorator][^MaxTimeDivision]]
+ * [[Execute Division Fixture multiple times using Loop Decorator][^MultipleDivision]]
+ * [[Example of piping !-MaxTime-! and Loop decorator to build complex decorators][^TimedMultipleDivision]]
+ * [[Measure if the Division Fixture is executed in the given Time Range using the !-TimeRange-! decorator][^TimeRangeDivision]]
+ * [[Copy the last row and append it to the end of the table 'n' number of times using !-CopyAndAppendLastRow-! decorator][^CopyAndAppendLastRow]]
+ * [[Increment all the subsequent column values using the !-IncrementColumnsValues-! decorator][^IncrementColumnsValues]]
+ * [[Example of piping !-CopyAndAppendLastRow-! and !-IncrementColumnsValues-! decorators][^CopyAppendLastRowAndIncrementColumnValues]]
+
+'''Note:''' !-FitDecorator-! does not support [[Fit Library][http://fitlibrary.sourceforge.net]] as of now. 
+
+!contents

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFitDecoratorTests/properties.xml

@@ -0,0 +1,12 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit/>
+	<Files/>
+	<Properties/>
+	<RecentChanges/>
+	<Suite/>
+	<WhereUsed/>
+	<saveId>1166331006945</saveId>
+	<secure-write/>
+	<ticketId>-455847644342679400</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/SuiteAcceptanceTests/SuiteFixtureTests/SuiteColumnFixtureSpec/TestArraysInColumnFixture/content.txt

@@ -0,0 +1,16 @@
+!3 You can put arrays of objects into ColumnFixture fixtures.
+
+!|fitnesse.fixtures.ComplexAddFixture|
+|a|b|sum?|
+|1,2|3,4|4,6|
+
+{{{
+public class ComplexAddFixture extends ColumnFixture
+{
+  public int[] a;
+  public int[] b;
+  public int[] sum() {
+    return new int[] {a[0]+b[0], a[1]+b[1]};
+  }
+}
+}}}