1. Article for last Tuesday u “Enhancing Software Testing by Judicious Use of Code Coverage Information” 1 540f07testing20nov06

2. 2 Would you like to work for this company? Why or why not?

3. Was there any group that did not use the new technology effectively? 3 540f07testing20nov06

4. Was there a better way to encourage technology transfer? 4 540f07testing20nov06

5. What was their approach to testing and was it great? 5 540f07testing20nov06

6. A set of sophisticated mocks to simulate the messaging infrastructure of the underlying enterprise service bus. 6 540f07testing20nov06

7. A user interface [2] to run all automated tests independently from the development environment. 7 540f07testing20nov06

8. Software Testing Structural testing revisited 8 540f07testing20nov06

9. Other test documents u test-case specification –inputs, outputs, procedures u test-procedure specification u test log u test-incident report u test-summary report

10. Other Testing Strategies u Performance Testing u Stress Testing u Worst Case Testing u Random Testing

11. Team Discussion - strategies u Do any of the list of testing strategies apply to your team project?

12. Testing Phases u module/unit testing u integration testing u system testing u validation/acceptance testing u regression testing

13. Integration Testing u top-down –code and test the top module first, using stubs to represent the uncoded modules u bottom-up –code and test the bottom modules first, using simple drivers to execute the modules u big-bang –doing everything at once

14. TTYP - Team - integration u How should your team do the integration testing of your project?

15. Other Testing Strategies u Performance Testing u Stress Testing u Worst Case Testing u Random Testing

16. partial contents of a Test Plan (IEEE Standard) u identifier u introduction u test items (what is to be tested) u features –to be tested –not to be tested u methodology u pass/fail criteria u suspension criteria u deliverables u responsibilities u schedule u contingency plans u approvals

17. Test Plan – part 1 u Identifier –A unique name, version number u Introduction –What is project, etc u test items (what is to be tested) –Specific identifier of items

18. Test Plan - part 2 u Features –to be tested »What functionality, capabilities –not to be tested »Is there anything to be excluded? u Methodology –Overview of approach

19. Test Plan – part 3 u Pass/fail criteria –When is testing through, positively or not u Suspension criteria –When is testing halted for more development, debugging work? u Deliverables –What reports, etc are delivered

20. Test Plan – part 4 u Responsibilities –Who is responsible for what tasks u Schedule u contingency plans –What if plans can not be followed u Approvals –Who approves what

21. Other test documents u test-case specification –inputs, outputs, procedures u test-procedure specification u test log u test-incident report u test-summary report

22. Future u Thurs, Nov 8 - Exam preview u Tues, Nov 13 - Exam