For example, you could be ordering tests so that the test that failed most
recently was executed first or the fastest tests executed first. That has
nothing to do with dependency.

I wrote a piece a few years ago where I identified different meanings for
dependency of tests...

Test A does some setup and test B depends on that setup being done. This
is "true" dependency and is generally considered evil in unit testing.
However, it's really not what most people mean when they ask for dependency.
Test A depends on a feature and tests it independently. Test B depends
on the same feature and some other feature in addition. While it's possible
to run test B even if A has failed, it's not useful. This is what most
folks seem to want when they ask for a dependency feature.
Tests A and B are actually independent, but test A is for something
really important. If it fails, we are going to fix it before anything else,
so we just want to quit at that point.
Tests A and B are actually independent, but a failure of Test A will
cause B to generate messages that are not really useful. We'd rather not
see the messages, although it's OK if we run the test.

A really useful implementation of test dependency would allow
distinguishing these cases. The user would specify the nature of the
dependency and the framework would decide how to deal with it. That's
different from Ordering, where we just tell the framework what to do
without giving our reasons.

For now, we're going to get out NUnit 3.0 without this feature.

On Fri, Aug 8, 2014 at 12:56 PM, voloda notifications@github.com wrote:

I see your point with Ordering vs. Dependency and I agree that it is
complicated - though - if you are trying order things it IMHO implies
dependency. And if the dependency failed the dependent test should fail as
well (otherwise the dependency does not make sense unless it is being used
for some tricky parallel execution logic).

If it will not fail it will most likely contain some conditional behavior
which should be IMHO avoided.

—
Reply to this email directly or view it on GitHub
#170 (comment)
.

Test Order Attribute #170

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions