xUnit

From Wikipedia, the free encyclopedia

Various code-driven testing frameworks have come to be known collectively as xUnit. Such frameworks are based on a design by Kent Beck, originally implemented for Smalltalk as SUnit, but are now available for many programming languages and development platforms.

Contents 1 xUnit Design 1.1 Test Fixtures 1.2 Test Suites 1.3 Test Execution 1.4 Assertions 2 A partial list of xUnit frameworks 3 External links

[edit] xUnit Design

The overall design of xUnit frameworks depends on several components.

[edit] Test Fixtures

A test fixture is the set of preconditions or state needed for a test to run. Also known as a test context.

[edit] Test Suites

A test suite is a set of tests that all share the same fixture.

[edit] Test Execution

The execution of an individual unit test proceeds as follows:

setup();
...
/* Body of test */
...
teardown();

The setup() and teardown() methods serve to initialize and clean up test fixtures.

[edit] Assertions

An assertion is a function or macro that verifies the behavior of the unit under test. Failure of an assertion typically throws an exception, aborting the execution of the current test.

[edit] A partial list of xUnit frameworks

• List of unit testing frameworks

[edit] External links

• Kent Beck's original testing framework paper
• Other list of various unit testing frameworks
• OpenSourceTesting.org lists many unit testing frameworks, performance testing tools and other tools programmers/developers may find useful
• Test automation patterns for writing tests/specs in xUnit.
• Martin Fowler on the background of xUnit.