[TIP] alphabetical order in testing

Michael Foord fuzzyman at voidspace.org.uk
Wed Jan 20 07:32:02 PST 2010

On 20/01/2010 15:26, Olemis Lang wrote:
> On Wed, Jan 20, 2010 at 10:17 AM, Olemis Lang<olemis at gmail.com>  wrote:
>> On Wed, Jan 20, 2010 at 9:52 AM, C. Titus Brown<ctb at msu.edu>  wrote:
>>> On Wed, Jan 20, 2010 at 09:12:29AM -0500, Olemis Lang wrote:
>>>> On Wed, Jan 20, 2010 at 5:42 AM, holger krekel<holger at merlinux.eu>  wrote:
>>>>> Some way of telling a test runner to consider tests in a certain
>>>>> order makes sense to me, though.
>>>>> In fact, I had user requests and own thoughts to allow declaring dependencies -
>>>>> such that if a test fails subsequent ones would not be run anymore.
>>>> Probably (I don't know the exact details ;o), but if the first test
>>>> fails that (should ?) means that something is not right (i.e. behaving
>>>> like expected) with the SUT .
>>> Olemis, et al. -- independence of test order is generally considered a
>>> requirement for unit tests, but not for other tests (functional, UI, etc.)
>>> where it simply wouldn't make sense.

I always write my function / integration tests to be order independent - 
grouping them in classes with common setup if the application needs to 
be put in a certain state for the tests to work.

Writing functional or UI tests to depend on each other seems to me just 
as bad as for unit tests.

Michael Foord

> BTW, D'u have some (concrete ?) examples illustrating this ?


READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

More information about the testing-in-python mailing list