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 page in debug mode source should contain text
check request page @source?test&debug 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.SetUp (edit)

Import
fitnesse.fixtures

SetUp


This test shows that the partitioner can work with a file containing the division of the suite, instead of calculating from scratch.
The file is specified by the partitionIndexFile parameter and should be placed in the files section.

The file may contain extra tests, they are ignored.
Tests not listed in the file are split across all partitions and put before the tests listed in the file.

---

variable defined: TEST_SYSTEM=slim

Create the file section
file section setup

Add some files
file section file adder
path type content valid?
partition.txt file Page Partition Test System Order SuitePage.TestPage1 2 fit 99 SuitePage.TestPage2 2 fit 0 SuitePage.TestPage3 1 fit 0 SuitePage.TestPage4 0 fit 0 SuitePage.TestPage5 0 fit 1 true

Create a Suite page

script Page Builder
line !path lib/*.jar
page SuitePage

Create two sub pages

script Page Builder
line |!-fitnesse.testutil.PassFixture-!|
page SuitePage.TestPage1

script Page Builder
line |!-fitnesse.testutil.PassFixture-!|
page SuitePage.TestPage2

script Page Builder
line |!-fitnesse.testutil.PassFixture-!|
page SuitePage.TestPage3

script Page Builder
line !define TEST_SYSTEM {slim}
page SuitePage.TestPage4

script Page Builder
line |!-fitnesse.testutil.PassFixture-!|
page SuitePage.TestPage6

script Page Builder
line |!-fitnesse.testutil.PassFixture-!|
page SuitePage.TestPage7

Response Requester.
uri valid?
SuitePage?responder=partition&format=tsv&partitionCount=3&partitionIndexFile=partition.txt true

Response Examiner.
contents?

The suite should report all TestPages in tab-separate format.

Response Examiner.
type pattern matches?
headers Content-Type: text/tab-separated-values true
contents Page\tPartition\tTest System\tOrder\n true
contents SuitePage\.TestPage1\t2\tfit\t1\n true
contents SuitePage\.TestPage2\t2\tfit\t0\n true
contents SuitePage\.TestPage3\t1\tfit\t1\n true
contents SuitePage\.TestPage4\t0\tslim\t1\n true
contents SuitePage\.TestPage6\t0\tfit\t0\n true
contents SuitePage\.TestPage7\t1\tfit\t0\n true

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


tear down

Keyboard Shortcuts ?

  • General

  • t Test page or suite
  • e Edit page
  • v View page (after test)
  • a Add new page

  • Go To

  • g u User Guide
  • g q Quick Reference Guide
  • g f Full Reference Guide
  • g c Recent Changes

  • Edit Mode

  • CTRL+s Save page
  • ESC Cancel edit

  • Tools

  • p Properties
  • w Where used?
  • AK+v Versions
  • AK+h Page History
  • / Focus on search bar
  • s Open search page
Close