The document discusses various types and stages of software testing in the software development lifecycle, including: 1. Component testing, the lowest level of testing done in isolation on individual software modules. 2. Integration testing in small increments to test communication between components and non-functional aspects. 3. System testing to test functional and non-functional requirements at the full system level, often done by an independent test group. 4. The document provides details on planning, techniques, and considerations for each type of testing in the software development and integration process.

1. Testing in the Lifecycle Software Testing Foundations 1 Principles 2 Lifecycle 4 Dynamic test techniques 3 Static testing 5 Management 6 Tools

2. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

3. V-Model: test levels Integration Testing in the Small Integration Testing in the Large System Testing Component Testing Acceptance Testing Code Design Specification System Specification Project Specification Business Requirements

4. V-Model: late test design Tests Business Requirements Tests Project Specification Tests System Specification Tests Design Specification Tests Code Integration Testing in the Small Integration Testing in the Large System Testing Component Testing Acceptance Testing “ We don’t have time to design tests early” Design Tests?

5. V-Model: early test design Tests Business Requirements Tests Project Specification Tests System Specification Tests Design Specification Tests Code Integration Testing in the Small Integration Testing in the Large System Testing Component Testing Acceptance Testing Tests Tests Tests Tests Tests Run Tests Design Tests

7. Experience report: Phase 1 Phase 1: Plan 2 mo 2 mo dev test test 150 faults 1st mo. 50 faults users not happy Quality fraught, lots of dev overtime Actual "has to go in" but didn't work

8. Experience report: Phase 2 Source: Simon Barlow & Alan Veitch, Scottish Widows, Feb 96 Phase 2: Plan 2 mo 6 wks dev test test 50 faults 1st mo. 0 faults happy users! Quality smooth, not much for dev to do Actual acc test: full week (vs half day) on time Phase 1: Plan 2 mo 2 mo dev test test 150 faults 1st mo. 50 faults users not happy Quality fraught, lots of dev overtime Actual "has to go in" but didn't work Phase 2: Plan 2 mo 6 wks dev test test 50 faults 1st mo. 0 faults happy users! Quality smooth, not much for dev to do Actual acc test: full week (vs half day) on time

10. Verification, Validation and Testing Verification Validation Testing Any

17. Cost of fixing faults Req Use Des Test 1 10 1000 100

19. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

28. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

32. Component Test Document Hierarchy Source: BS 7925-2, Software Component Testing Standard, Annex A Component Test Strategy Project Component Test Plan Component Test Specification Component Test Plan Component Test Report

33. Component test process Checking for Component Test Completion Component Test Planning Component Test Specification Component Test Execution Component Test Recording BEGIN END

34. Component test process Component Test Planning Component Test Specification Component Test Execution Component Test Recording Checking for Component Test Completion BEGIN END Component test planning - how the test strategy and project test plan apply to the component under test - any exceptions to the strategy - all software the component will interact with (e.g. stubs and drivers

35. Component test process Component Test Planning Component Test Specification Component Test Execution Component Test Recording Checking for Component Test Completion BEGIN END Component test specification - test cases are designed using the test case design techniques specified in the test plan (Section 3) - Test case: objective initial state of component input expected outcome - test cases should be repeatable

36. Component test process Component Test Planning Component Test Specification Component Test Execution Component Test Recording Checking for Component Test Completion BEGIN END Component test execution - each test case is executed - standard does not specify whether executed manually or using a test execution tool

37. Component test process Component Test Planning Component Test Specification Component Test Execution Component Test Recording Checking for Component Test Completion BEGIN END Component test recording - identities & versions of component, test specification - actual outcome recorded & compared to expected outcome - discrepancies logged - repeat test activities to establish removal of the discrepancy (fault in test or verify fix) - record coverage levels achieved for test completion criteria specified in test plan Sufficient to show test activities carried out

38. Component test process Component Test Planning Component Test Specification Component Test Execution Component Test Recording Checking for Component Test Completion BEGIN END Checking for component test completion - check test records against specified test completion criteria - if not met, repeat test activities - may need to repeat test specification to design test cases to meet completion criteria (e.g. white box)

40. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

55. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

69. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

73. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

76. User Acceptance testing 20% of function by 80% of code System testing distributed over this line Acceptance testing distributed over this line 80% of function by 20% of code

80. Acceptance testing motto If you don't have patience to test the system the system will surely test your patience

81. Contents Models for testing, economics of testing High level test planning Component Testing Integration testing in the small System testing (non-functional and functional) Integration testing in the large Acceptance testing Maintenance testing Lifecycle 1 2 3 4 5 6

86. Summary: Key Points V-model shows test levels, early test design High level test planning Component testing using the standard Integration testing in the small: strategies System testing (non-functional and functional) Integration testing in the large Acceptance testing: user responsibility Maintenance testing to preserve quality Lifecycle 1 2 3 4 5 6