| Task Descriptor: Write Unit Test |
| |
Relationships
| Roles | Primary:
| Additional:
| Assisting:
|
| Inputs | Mandatory:
| Optional:
| External:
|
| Outputs |
|
Steps
|
General
| When looking at an Engineering Task, you should consider how to add the capability to the system. Does the system require
new classes? Are there classes that would be useful? Regardless of how these decisions come out, the addition of
functionality requires the creation of a test case. You write the test case to demonstrate that a portion of the
functionality you need isn't in the system. This test case should fail. |
|
Properties
| Predecessor |
|
| Multiple Occurrences |  |
| Event Driven | |
| Ongoing | |
| Optional | |
| Planned | |
| Repeatable |  |
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
|
|
