For distributed testing or to debug fixture code locally it can be helpful to connect to a manually started SlimService

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.SuiteSlimTests.SetUp (edit)

Import
fitnesse.fixtures

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

Library
page driver
echo fixture

The below configuration option is useful in two scenarios

1) Pretesting on a developer workstation

GIVEN you run a central FitNesse Wiki
WHEN your developer did some code changes on his workstation
AND he wants to see if the test still pass
THEN you can start a SlimService on his workstation manual
AND can execute all tests from your central Wiki

2) Distributed Testing

Given you run a central FitNesse Wiki on Linux
WHEN you need to test some .net code on Windows
THEN you can start a .Net SlimService on your Windows Server manual and run it in daemon mode
AND can execute the test case from your central Wiki

Configure the test system as below:

!define MANUALLY_START_TEST_RUNNER (true)
!define slim.pool.size (1)
!define SLIM_PORT {YOUR TEST PORT}
!define SLIM_HOST {WORKSTATION or SERVER NAME}


To demonstrate this we connect to the local Fitnesse Wiki webserver. This should connect but fail with a message that no Slim Header has been provided.
Tip: Increase the slim.timeout if you need more time to startup the SlimService manual
Important: !define slim.pool.size (1) to avoid to try any other port than the port you specified.
Note: if run from Junit no wiki server is started and this test would fail. The tag 'noJunit' has been added to remove it from Junit testing. :)

script
create page TestPage with content !define TEST_SYSTEM {SLIM} !define slim.timeout {1} !define MANUALLY_START_TEST_RUNNER (true) !define slim.pool.size (1) !define SLIM_PORT {8080} !define SLIM_HOST {127.0.0.1}
check request page TestPage?test 200
ensure content matches class="error".{0,60}SlimError: Timeout while reading slim header from client. Check that you are connecting to the right port and that the slim client is running.
show collapsed content
check request page TestPage?executionLog 200
ensure content matches Command.{0,20}Connection to running SlimService: 127.0.0.1:8080
show collapsed content

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