Included page: .FitNesse.SuiteAcceptanceTests.ScenarioLibrary (edit)

scenario given page page with content content
create page @page with content @content
$IT= echo @page

scenario given page page
given page @page with content nothing
$CONTENT= echo

scenario given test page page
given page @page
make @page a test page

scenario given slim test page page
given page @page with content !define TEST_SYSTEM {slim}
make @page a test page

scenario page source should have link to target
check request page @source 200
ensure content contains <a href="@target"
$IT= echo @source

scenario it should have link to target
page $IT should have link to @target

scenario and it should have link to target
page $IT should have link to @target

scenario page source should have creating link to target
check request page @source 200
ensure content contains @target<a title="create page" href="@target?edit&nonExistent=true">[?]</a>

scenario it should have creating link to target
page $IT should have creating link to @target

scenario page source should contain text
check request page @source 200
ensure content contains @text
show content

scenario page source should not contain text
check request page @source 200
reject content contains @text
show content

scenario page source should match text
check request page @source 200
ensure content matches @text
show content

scenario it should contain text
page $IT should contain @text

scenario it should not contain text
page $IT should not contain @text

scenario it should contain text in line symbol
check request page $IT 200
$@symbol= line number containing @text

scenario it should match text
page $IT should match @text

scenario test results for page source should contain text
check request page @source?test 200
ensure content contains @text
show content

scenario test results for suite source should contain text
check request page @source?suite 200
ensure content contains @text
show content

scenario its test results should contain text
test results for page $IT should contain @text

scenario test ressults for page source should not contain text
check request page @source?test 200
reject content contains @text
show content

scenario and should contain text
ensure content contains @text
show content

scenario and should match text
ensure content matches @text
show content

scenario and should not contain text
reject content contains @text
show content

scenario widget wikiText should render htmlText
create page WidgetPage with content @wikiText
check request page WidgetPage 200
ensure content matches @htmlText
show content

scenario the line after should come after before
check echo int $@before < $@after

scenario pass
check echo pass pass

scenario show collapsed content
show @content

scenario show Symbol result

scenario then pass assertions pass, fail fail, ignore are ignored exception exceptions thrown
ensure content matches Assertions:<[^<]*@pass right, @fail wrong, @ignore ignored, @exception exceptions
show extract match; Assertions:<[^<]*exceptions contents 0

scenario and cell text has result result
ensure content matches class="@result">@text<
show extract match; class="[^"]+">@text< contents 0

variable defined: TestSTART=@@@START: Test specific content
variable defined: TestEND=@@@END: Test specific content

scenario and TestSystem setup is content
$CONTENT= echo $CONTENT @content

scenario and setup content is content
$CONTENT= echo $CONTENT @content

scenario and test content is content
given page $IT with content $CONTENT @@@START: Test specific content@content@@@END: Test specific content
make $IT a test page

scenario get HTML result
start Response Examiner.
setType contents
setPattern @@@START: Test specific content[^<]*(.*>)\s*@@@END: Test specific content
setGroup 1
$HTML_Result= found

scenario get HTML input
start Response Examiner.
setType pageHtml
setPattern @@@START: Test specific content[^<]*(.*>)\s*@@@END: Test specific content
setGroup 1
$HTML_Input= found
show collapsed get value


scenario get collapsed executon log for page source
check request page @source?executionLog 200
show content

scenario when page source is tested
check request page @source?test 200
show collapsed content

scenario when page source is tested and HTML is extracted
when page @source is tested
get HTML result
get HTML input

Included page: .FitNesse.SuiteAcceptanceTests.SuiteSlimTests.SetUp (edit)

Import
fitnesse.fixtures

SetUp Plugins=fitnesse.testsystems.slim.CustomTableAliasPlugin CustomComparators=glob:fitnesse.testsystems.slim.GlobComparator

Library
page driver
echo fixture

If a decision table is implemented with a class you can specify constructor arguments.
See .FitNesse.UserGuide.WritingAcceptanceTests.SliM.ConstructorArguments for details.

If a decision table is implemented with a scenario you can specify constructor arguments as well they have the following meaning:

scenario Division _ _ _ numerator, denominator, quotient?
setNumerator @numerator
setDenominator @denominator
$quotient= quotient

library
eg.Division

Calling a Scenario with Constructor Parameters


The input variable "numerator" is given on the table construction line and must not be repeated in each row.
This can make the decison tables more readable.

Division having numerator 9
denominator quotient?
3 3.0
2 4.5

The Syntax is - Scenario Name - [given|having] - 1. Variable Name - 1. Variable Value - 2. Variable Name - 2. Variable Value - ....

To ensure backward compatibility constructor parameters are first checked if they are part of a scenario name
If a senario is found it will be used and no constructor values are passed.
Only if no such scenario is found the constructor parameters can be used.

Example:

Again a scenario with the same signature as above
scenario Division _ _ _ numerator, denominator, quotient?
check echo @numerator 7

Division having numerator 7
denominator
3

Now a higher priority scenario name
This new scenario has a name which matches the constructor parameter name "numerator".
Calling again the same decision table will use this scenario.
But numerator will not have a value.
scenario Division Numerator _ _ _ numerator, denominator, quotient?
check echo @numerator @numerator
check not echo @numerator 12


Division having numerator 12
denominator
3

Scenario without output parameters can be used as well with constructor parameters

In this case the full line will be collered with the scenario test result. In scenarios with output parameters only the output column cells are colored.
scenario myDivision _ _ _ numerator, denominator, quotient
setNumerator @numerator
setDenominator @denominator
check quotient @quotient

myDivision having numerator 12
denominator quotient
3 4.0
6 2.0
4 3.0

Included page: .FitNesse.SuiteAcceptanceTests.TearDown (edit)



tear down