Task Descriptor: Implement Developer Tests |  |
Implement one or more tests that enable the validation of the individual software components through execution.
Based on Method Task: Implement Developer Tests
Relationships
Roles | Main: Developer | Additional: Tester | Assisting:
Inputs | Mandatory: Implementation | Optional: Design | External: None
Outputs | Developer Test
Steps
Refine scope and identify the test(s)
Select the increment of work to be tested and identify developer test(s) to verify that the Implementation being developed behaves correctly. One source for the expected behavior for a software component is the Design. In identifying the tests or in any other part of this task, consider collaborating with a Tester who should be well-versed in the issues of testing.
Write the test setup
To successfully run a test the system must be in a known state so that the correct behavior can be defined. Implement the setup logic that must be performed as part of the Developer Test.
Define the expected results
Define the expected results of each test so that it can be verified. After a test runs, you need to be able to compare the results of running the test against what was expected to happen. The test is successful when the actual results match the expected results.
Write the test logic
Write the steps that perform the actual test(s).
Define the test response
Define the information the test(s) must produce to successfully indicate success or failure. Consider if a response of True or False is sufficient, or if a detailed message should be logged as well.
Write clean-up code
Identify, and then implement, the steps to be followed in order to restore the environment to the original state for each test. The goal is to ensure that there are no side effects from running the tests.
Test the test
Verify that each developer test works correctly. To do this: Run the test(s), observe their behavior, and fix any defects in the tests. Ensure that the expected results are defined properly and that they're being checked correctly. Check the clean-up logic for each test. Ensure that each developer test works within your test suite framework.
Properties
Multiple Occurrences |
Event-Driven |
Ongoing |
Optional |
Planned |
Repeatable |
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.