The order of tests in a test suite

[Teg Ryan]

Hi all,

What is the proper way to chain tests together in a test suite?  I have a series of tests that I want to perform, and have linked them all together using extenion points.  However, some of the tests seem to be run multiple times if I do it that way.  I tried making them all sub tests, and that works and seems to improve performance but when I move the test suite over to our dev server and run it from maven it now says "unable to start Firefox and open initial URL" and the test that it fails on is the LAST one of the test group.  It looks like it starts with the last one in the suite, which is also alphabetically the first test.

Anyone care to comment on the proper way to chain tests together in a test suite so that I can run them straight from maven on a different box?

Thanks,

Teg

[Teg Ryan]

OK, I've figured this out. When you run the test suite from Maven, it
runs the custom.testsuitetest.java class instead of the .ats file.
It's all in the docs but I didn't understand that on the first couple
of passes. So in there you specify the order of your tests if you
want to run it from Maven, which by default simply scans the test
directory and runs them in the order it finds them (hence the
alphabetical order described above).

In short, your testsuite.ats file is only useful in CubicTest (or I
presume if you export to selenium HTML files) and has no relation or
bearing at all if you run the tests as Junit tests.

Hope that helps someone who had the same issue as me.

Teg