|
Purpose
-
Execute the automated unit test and gather results.
|
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
Steps
|
General
| This task consists of running all the unit tests to ensure that software units are still working. If unit test is executed
before new code is added (new feature is implemented), then that test results helps programmer to find out what code
changes he needs to implement. If test doesn't pass, then programmer fixes code and try to pass test again until tests
finally pass. The idea is to write failing test, so it covers some case or new functionality which is not implemented in
current code base. A lot of XP teams run those tests on a daily basis as part of their automated daily build. Other teams
run those tests every time a new story is added to the pool of completed stories to ensure that a new story has not caused
previous ones to fail. |
|
More Information
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
|
|
