VERSION: Fitnesse 20070619
VERSION: Fitnesse 20080511 source snapshot
EXAMPLE: Directory tree
FitNesseRoot/
+-- TestBed/SystemA -- TEST_RUNNER w/ args
| +-- TestSuite/ -> .TestSuite/
| +-- TestSuite2/ -> .TestSuite2/
+-- TestSuite/
| +-- SuiteA/
| +-- ...
+-- TestSuite2/
| +-- SuiteA/ -> .TestSuite/SuiteA/
| +-- ...
DESCRIPTION:
- TestSuite2/ reuses a suite from TestSuite/.
- TestBed.SystemA/ contains the TEST_RUNNER variable and args specific for SystemA.
- Symlinks are use to reuse an compose other suites.
- TestSuite2 is for example a smaller testsuite that should execute fast.
- You may have many TestBed.System${X} ...
SYNDROME:
The problem seems to occur when the second level of symlinks is reached. The first level of symlinks is fine.
When you navigate from "TestBed.SystemA" down to "TestBed.SystemA.TestSuite2.SuiteA", you will:
- get an empty page (Fitnesse 20070619)
- a valid suite page (Fitnesse 20080511 source snapshot), but the "TestBed. ..." context (page title) is lost. Not the URL in the browser is still correct.
With the newer fitnesse version, you can execute the testsuite, but you cannot enter down the tests of the suite and execute each test because the "TestBed. ..." context is lost and therefore the TEST_RUNNER is undefined.
Log in to post a comment.
