Task: Run Developer Tests |
Run tests of the individual software components to verify that their internal structures work as specified.
Disciplines: Implementation
Purpose
To verify that the implementation works as specified.
Relationships
Roles | Primary Performer: Developer | Additional Performers: Tester
Inputs | Mandatory: Developer Test Implementation | Optional: None
Outputs | Test Log
Steps
Run tests
Run the Developer Tests. The procedure will vary, depending on whether the test is manual or automated and whether additional test components are necessary, such as drivers or stubs. To run the tests, you need to make sure that you have initialized the test environment with all necessary elements, such as software, hardware, tools, data, and so on. Automated tests will often update a Test Log which you can evaluate to determine where your tests went wrong.
Evaluate execution of tests
Testing ends or terminates in one of two conditions: Normal: The test run appears successful. You may choose to review the test log to ensure that this in fact is the case. For example, perhaps a developer test ran successfully but logged results which you didn't expect. Abnormal or premature: The developer tests did not run completely or as you intended. When testing ends abnormally, the test results may be unreliable. You must must identify and correct the cause of the termination and rerun the tests before you perform any additional test tasks.
Determine cause of the problem(s)
Review the test log to understand any reported failures, warnings, or unexpected results. The cause of the problem(s) may fall under one or more of the following categories The implementation element being tested is faulty. There is a problem with the developer tests. Perhaps there is a problem with the setup of a test, incorrect test data, or a test didn't evaluate its results appropriately. There is an environment problem. There may have been a fatal error (a network failures, a hardware crash, ...) or a test script command failure where a test script cannot execute a command or a line of code. Both types of abnormal termination of testing may exhibit the same symptoms, either unexpected actions or the test environment appearing to be unresponsive or in an undesirable state.
Take corrective action(s)
Based on the cause of the problem, determine the appropriate corrective action to recover from a "failed" test run. If the implementation element under test is faulty, fix the problem if possible. If the problem is serious and cannot be immediately addressed, perform the task Request Change to report the defect. If there was a problem with your environment, then fix it and then rerun your tests.
Key Considerations
It is common to require that code pass all Developer tests before it can be delivered in an integrated build (see Guideline: Promoting Builds). Pair with the Tester during all steps of this task to gain insight on testing and quality considerations.
More Information
Guidelines | Maintaining Automated Test Suite Programming Automated Tests Developer Testing
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright