Note that there are some explanatory texts on larger screens.

plurals
  1. POFitnesse framework very slow when folder depth is greater 4 - why?
    primarykey
    data
    text
    <p>We are currently establishing fitnesse as the testing tool user acceptance testing. So far everything is good. we are using the java version "20091121". We are having troubles with folders that are deeper than 4.</p> <p>We have setup the following folder structure:</p> <blockquote> <p>SetUp</p> <p>TestSuite</p> <p>content.txt + properties.xml (just "!contents" inside)</p> <blockquote> <p>UseCase2204</p> <p>content.txt + properties.xml (just "!contents" inside)</p> <blockquote> <p>SingleRequest02</p> <p>content.txt + properties.xml (just "!contents" inside)</p> <blockquote> <p>PositiveTest</p> <p>content.txt + properties.xml (just "!contents" inside)</p> <blockquote> <p>OneAdultWithChild</p> <p>here content.txt + properties.xml for the actual test containing 18 fixture tables</p> </blockquote> </blockquote> </blockquote> </blockquote> </blockquote> <p>When we start fitnesse and navigate to the deepest folder ("OneAdultWithChild") it takes roundabout 10 seconds until the page is displayed. Now, when I move the content up one hierarchy level (into "PositiveTest") the page takes 3 seconds to render. When I put the test content on the second level ("UseCase2204") it almost displays in a instant.</p> <p>The same behaviour happens during test executing. After pressing the "test" button the tests take:</p> <ul> <li>second level: 12 seconds</li> <li>fourth level: 14 seconds</li> <li>fifth level: 40 seconds! (plus, it takes ages until the "result captured" button appears)</li> </ul> <p>Now, I am stuck with this. We need this deeply nested structure to group all the tests. But if there is no solution or workaround we can't use fitnesse and i will be a big idiot for promoting the framework. In the past I've had positive results with fitnesse but we didn't have these deeply nested structures.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload