Test Execution

Registered by Charlie Poole

Currently, the sequencing of tests is the responsibility of the tests themselves. That is, each test suite executes its own child tests and each test reports its own results.

The absence of a distinct test execution object makes it difficult to support certain features, such as high-level setup and teardown, parallel test execution and cancellation of running tests with restart.

In NUnit 3.0, the objects representing tests will no longer have the responsibility of running any subordinate tests and a separate test runner will sequence through the tests to execute them in the desired order.

Blueprint information

Status:
Not started
Approver:
NUnit Developers
Priority:
Essential
Drafter:
Charlie Poole
Direction:
Needs approval
Assignee:
Charlie Poole
Definition:
Drafting
Series goal:
Accepted for trunk
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.