Test implementation and execution
- 1. Test Implementation and Execution Wahyudi Bayu Putra 11453101594 Sistem Informasi Sains dan Teknologi UIN Suska Riau
- 2. Test Implementation and Execution During test implementation and execution, we take the test conditions and make them into test cases and testware and set up the test environment. This means that, having put together a high-level design for our tests, we now start to build them. We transform our test conditions into test cases and procedures, other testware such as scripts for automation.
- 3. Test Implemention and Execution We also need to set up an envi- ronment where we will run the tests and build our test data. Setting up environ- ments and data often involves significant time and effort, so you should plan and monitor this work carefully.
- 4. Test implementation and execution have the following major tasks, in approximately the following order: Implementation Execution
- 5. Implementation We will also write instructions for carrying out the tests (test procedures). For the driving examiner this might mean changing the test condition 'junc tions' to 'take the route down Mayfield Road to the junction with Summer Road and ask the driver to turn left into Summer Road and then right into Green Road, expecting that the driver checks mirrors, signals and maneuvers correctly, while remaining aware of other road users.' We may need to automate some tests using test harnesses and automated test scripts.
- 6. Implementation Create test suites from the test cases for efficient test execution. A test suite is a logical collection of test cases which naturally work together. Test suites often share data and a common high-level set of objectives. We'll also set up a test execution schedule. Implement and verify the environment. We make sure the test envi ronment has been set up correctly, possibly even running specific tests on it.
- 7. Execution Execute the test suites and individual test cases, following our test proce dures. We might do this manually or by using test execution tools, accord ing to the planned sequence. Log the outcome of test execution and record the identities and versions of the software under test, test tools and testware. We must know exactly what tests we used against what version of the software; we must report defects against specific versions; and the test log we keep provides an audit trail. Compare actual results (what happened when we ran the tests) with expected results (what we anticipated would happen).
- 8. Execution Where there are differences between actual and expected results, report discrepancies as incidents. We analyze them to gather further details about the defect, reporting additional information on the problem, identify the causes of the defect, and differentiate between problems in the software and other products under test and any defects in test data, in test documents, or mistakes in the way we exe cuted the test. We would want to log the latter in order to improve the testing itself. Repeat test activities as a result of action taken for each discrepancy. We need to re-execute tests that previously failed in order to confirm a fix (confirmation testing or re-testing). We execute corrected tests and suites if there were defects in our tests. We test corrected software again to ensure that the defect was indeed fixed correctly (confirmation test) and that the programmers did not introduce defects in unchanged areas of the software and that fixing a defect did not uncover other defects (regression testing).
- 9. Referensi
- 10. BackLink http://sif.uin-suska.ac.id/ http://fst.uin-suska.ac.id/ http://www.uin-suska.ac.id/
- 11. Thank you