2 Introduction to Test Purposes of Implementation Plan the integration tests for each build and system tests at the end of each iterationDesign and implement the tests by creating test cases that specifies what to test and test procedurePerform the tests and systematically handle the results of each test
3 Artifacts of Implement. - Overview Test ModelTest casesTest proceduresTest componentsTest planDefectsTest Evaluation
4 Artifacts – Detailed Test model Describe how executable components in the implementation model are tested by integration and system tests.Describe how specific aspects of the systems are to be tested if needed.A test model is a collection of test cases, test procedures, and test components
5 Artifacts – Test Cases Test cases A test case specifies on way of testing the system, including input, output and testing conditionsCommon test cases:A test case that specifies how to test a use case or a scenario of a use case. It includes verifying the results and the sequence of interactions, and the pre- and post conditions. “Black-box” test (p298, example)A test case that specifies how to test a use-case realization – design or a specific scenario of the realization. It verifies the interaction between components implementing the the use case. “White box” test
6 Artifacts – Test Cases Test cases Other test cases: Installation tests: verify that the system can be installed on the customer platform and operates correctly.Configuration tests: verify that the system works correctly in different configurations, such as different network configurationsNegative tests: try to cause the system to fail to find its weakness, such as impossible work loadStress tests: Identify problems with the system when it suffers insufficient system resources, like memory, disk space
7 Artifacts – Test Procedure, etc. Specifies how to perform one or several test cases or parts of them (p300 example and p301 example)Test componentA test component automates one or several test procedures. Also called test drivers, test harnesses, and test scriptsTest planDescribes the testing strategies, resources and schedule by defining the kinds of test for each iteration, their objectives, and test coverage.DefectA defect is a system anomaly.Test evaluationAn evaluation of the results of the test efforts like test coverage, etc.
8 Activities of Test - Overview Plan testPlan the testing efforts for each iteration.Design testDesign test cases and test proceduresImplement testAutomate test procedures by creating test componentsPerform integration testPerform integration tests for each buildPerform system testPerform system tests at the end of each iterationEvaluate test
9 Test Plan Steps: (p306, example) Describe a testing strategyEstimate the requirements for the testing effort, such as human and system resourcesSchedule the testing effortIdentify test cases, procedures, and components that gives the best returns on investment in terms of the improved quality
10 Design Test – Integration Test Design integration test casesVerify that the components interact with each other properly after they are integrated in each buildMost integration test cases can be derived from use-case realization – design through interaction diagramsThe actual interactions among components are compared with the interactions in the interaction diagrams
11 Design Test – System Test Design system test casesTest the system functions correctly as a whole.Test primarily tests combinations of use cases instantiated under different conditionsPrioritize combinations of use-cases thatAre required to function in parallelAre likely to be performed in parallelAre likely to influence each other if in parallelInvolve multiple processes
12 Design Test - Regression Design regression test casesSome test cases from earlier builds may be used for regression tests in subsequent testIdentify those test cases for regression testsIdentify and structure test proceduresSpecify test procedures for each test caseReuse test procedures as much as possibleSpecify how to test classes in one service system if possible so when the service system changes, only the test cases related it need to be re-designed
13 Implement Test Implement test Perform integration test Automate test procedures by creating test components, if possible.Perform integration testExecute the test procedures manually or automaticallyCompare the test results with the expectedReport the defects to component engineer who is responsible for the components that are likely to contain the faultReport the defects to the test designer for test evaluation
14 Evaluate Test Evaluate test Evaluate the results of the test effort by comparing the results with the goals outlined in the test planDefect trend analysis:Testing completeness: indicate what percentage of test cases that have been executed and what percentage of the code that have been coveredReliability: predicted # of bugs in the systemBased on defect trend analysis, further actions are determined:Add more tests to locate more defectsRelax the criteria for the tests
15 Perform Unit Test Structure testing or white-box testing Verify the unit’s internal implementationEvery statement is executed at least once.Test the most interesting paths through the codeMost commonly followed pathsMost critical pathsThe least-known pathsHigh risk paths
16 Summary of Test Test model: Test Activities Test cases Test procedures Test componentsTest ActivitiesPlan testDesign testImplement testPerform integration testPerform system testEvaluate test
Your consent to our cookies if you continue to use this website.