The FAQ for CubitTest mentioned that looping or cycling among tests/pages/states would be complicated. http://boss.bekk.no/display/BOSS/CubicTest+-+FAQ

Could there be other ways to work toward the goal, even if the graphical editor does not initially support cycling? If I want CT to repeat a test (run it multiple times), I currently have to list the test multiple times as a subtest or a test within a suite.

Here are some ideas for future CT enhancement:

- Have a "number of times to run" attribute for each test or subtest. The test would run x number of times without variations.

- For parameterized tests, have an option to auto-increment the index after each run and then run again until all values are used.

- In the test export process (for Watir/Selenium/etc.), have an option for "number of times to run" that inserts a loop template into the script.