how do i specify order of tests to run in windmill

[pusan]

I have 50 tests, 20 of those depends on the other 30.
The way I can think of is to put first 30 in __inti__.py, then use
Hudson to run the other 20, all of the 20 tests are put in a
directory.
I am wondering if anyone has better idea of how to organize all these
tests.
Thanks a lot.

[Mikeal Rogers]

In windmill's Python framework and in nose you can create dependencies in tests by using setup/teardown in the module hierarchy but you cannot create explicit ordering.

I do believe the javascript framework has a way to specify explicit ordering in addition to setup/teardown hierarchies.

Ordering in general should be avoided if you ever intend on running tests concurrently to speed up run times.

-Mikeal

[pusan]

Thanks for reply, Kind of disappointed by this.
Generally, I am wondering if anyone can recommend any good strategy
for scenario like this:
User sign up with different permission. (first group of tests, 1
original user, then he invited other people to sign up)
User log in and testing different permission (second group)
You can see, there are strong dependency among the tests.
How can windmill framework apply to these tests.
Thanks in advance for any suggestions/replies.

[Martin Häcker]

> Thanks for reply, Kind of disappointed by this.
> Generally, I am wondering if anyone can recommend any good strategy
> for scenario like this:
> User sign up with different permission. (first group of tests, 1
> original user, then he invited other people to sign up)
> User log in and testing different permission (second group)
> You can see, there are strong dependency among the tests.
> How can windmill framework apply to these tests.
> Thanks in advance for any suggestions/replies.

We have the same requirement and you can take a look at the source of
agilo if you want to see how we do it. Get it at
<http://www.agile42.com/cms/pages/agilo/> (need to download the source code)

In a nutshell:
* We adapted unittest.TestCase to be able to use windmill
* We added the concept of environments to this (we have a superclass for
all our tests) so the browser is brought up by the first test that needs
it and brought down by the last test that uses windmill.
* Each testClass has one setUp(self): method that does all the
dependency setup
* There's more, but that should give you the idea.

Regards,
Martin