Artifact: XP Unit Test

Used to ensure that a specific functionality of a component of the system is working properly.

Purpose

An XP Unit Test is written by developers to ensure that all system components work as expected. XP Unit Test give the developers the confidence to modify the system and feel confident that everything still works.

Relationships

Roles	Responsible: XP Programmer	Modified By: XP Programmer
Tasks	Input To: Refactor Code	Output From: Implement Spike Refactor Code

Description

Main Description

XP Unit Tests are usually implemented at the class level (in OO languages) and test the public interface. For every class in the system, a test class exists. Popular test frameworks are available usually for free (such as JUnit, CppUnit, CppUnitLite, NUnit). These are simple tools that help the developer to organize and run unit tests. These tests drive the programmer development and tell the programmer that the code works as the programmer expects.

Illustrations

Examples	Test-Ideas Catalog Examples

More Information

Concepts	Developer Testing Test Driven Development Test-first Design
Guidelines	Equivalence Class Analysis Test Ideas for Booleans and Boundaries Test Ideas for Method Calls Test Ideas for Statechart and Flow Diagrams

Copyright (c) 2002, 2006 IBM Corporation and Object Mentor. All rights reserved.
This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html.
Contributors: IBM Corporation and Object Mentor - initial implementation