NUnitLite Features

The following features are available in the current release

TestCases
Test fixtures may be created by inheriting from the TestCase class. Any methods begining with the case-insensitive prefix "test" are identified as tests. SetUp and TearDown may be overridden and will be called before and after each test.

TestFixtures
A non-TestCase class may be used as a fixture by marking it with the TestFixtureAttribute. Within such a class, test methods are marked by the TestAttribute, setup by the SetUpAttribute and teardown by the TearDownAttribute. The ExpectedExceptionAttribute is also supported on test methods.

Note: TestFixtureAttribute, TestAttribute and ExpectedExceptionAttribute may also be used on TestCase-derived classes. SetUpAttribute and TearDownAttribute are ignored on such classes.

TestSuites
By use of the static Suite property, arbitrary suites of tests may be manually created. A suite may consist of individual test cases, entire test fixtures or other suites.

Asserts
The programmer expresses expected test conditions using the Assert class. The existing functionality of most current NUnit Assert methods is supported, but the syntax has been changed to use a more extensible format.

Running Tests
Tests are loaded as a list of fixtures, without any additional hierarchy. Each fixture contains it's tests. Tests are executed in the order found, without any guarantees of ordering. A separate instance of the fixture object is created for each test case executed by NUnitLite.

Console Runner
The embedded console runner produces a summary of tests run and lists any errors or failures.

Deployment
The current release is only suitable for embedded use. Tests are created in an exe project and the NUnitLite files may be included in the same project or compiled separately. In the case of separate compilation, the test project must include a small stub that starts NUnitLite execution.

Last edited Aug 29, 2006 at 9:24 PM by cpoole, version 14

Comments

No comments yet.