The document discusses various aspects of test management including organizational structures for testing, configuration management, test estimation and monitoring, incident management, and standards for testing. It describes different levels of independence for testing, such as testing by developers, testing by development teams, and independent test teams. It also outlines the importance of configuration management, estimating and measuring test progress, logging incidents, and following standards for quality assurance and industry-specific testing.

1. Test Management Software Testing ISEB Foundation Certificate Course 1 Principles 2 Lifecycle 4 Dynamic test techniques 3 Static testing 5 Management 6 Tools Chapter 5

2. Contents Organisation Configuration Management Test estimation, monitoring and control Incident management Standards for testing Test Management 1 2 4 5 3 6 ISTQB / ISEB Foundation Exam Practice

3. Importance of Independence Time No. faults Release to End Users

14. Contents Organisation Configuration Management Test estimation, monitoring and control Incident management Standards for testing Test Management 1 2 4 5 3 6 ISTQB / ISEB Foundation Exam Practice

18. Configuration identification Configuration Identification Configuration Control Status Accounting Configuration Auditing Configuration Structures CI Planning Version/issue Numbering Baseline/release Planning Naming Conventions CI: Configuration item: stand alone, test alone, use alone element Selection criteria

19. Configuration control Configuration Identification Configuration Control Status Accounting Configuration Auditing CI Submission Withdrawal/ Distribution control Status/version Control Clearance Investigation Impact Analysis Authorised Amendment Review/ Test Controlled Area/library Problem/fault Reporting Change Control Configuration Control Board

20. Status accounting & Configuration Auditing Configuration Identification Configuration Control Status Accounting Configuration Auditing Status Accounting Database Input to SA Database Queries and Reports Data Analysis Traceability, impact analysis Procedural Conformance CI Verification Agree with customer what has been built, tested & delivered

22. Contents Organisation Configuration Management Test estimation, monitoring and control Incident management Standards for testing Test Management 1 2 4 5 3 6 ISTQB / ISEB Foundation Exam Practice

25. Test cycles / iterations Debug D R D R 3-4 iterations is typical Test Theory: Test Practice: Des Ex Ver Bld Iden Retest Retest

28. Measuring test execution progress 1 tests run tests passed tests planned now release date what does this mean? what would you do?

29. Diverging S-curve poor test entry criteria ran easy tests first insufficient debug effort common faults affect all tests software quality very poor tighten entry criteria cancel project do more debugging stop testing until faults fixed continue testing to scope software quality Note: solutions / actions will impact other things as well, e.g. schedules Possible causes Potential control actions

30. Measuring test execution progress 2 tests planned run passed action taken old release date new release date

31. Measuring test execution progress 3 tests planned run passed action taken old release date new release date

32. Case history Source: Tim Trew, Philips, June 1999

34. Entry and exit criteria Test Phase 1 Test Phase 2 "tested" is it ready for my testing? Phase 2 Phase 1 Entry criteria Exit criteria Acceptance criteria Completion criteria

37. Contents Organisation Configuration Management Test estimation, monitoring and control Incident management Standards for testing Test Management 1 2 4 5 3 6 ISTQB / ISEB Foundation Exam Practice

40. Use of incident metrics Is this testing approach “wearing out”? What happened in that week? We’re better than last year How many faults can we expect?

41. Report as quickly as possible? report 5 test can’t reproduce - “not a fault” - still there can’t reproduce , back to test to report again insufficient information - fix is incorrect dev 5 reproduce 20 fix 5 re-test fault fixed 10 dev can’t reproduce incident report test 10

47. Contents Organisation Configuration Management Test estimation, monitoring and control Incident management Standards for testing Test Management 1 2 4 5 3 6 ISTQB / ISEB Foundation Exam Practice

49. Summary: Key Points Independence can be achieved by different organisational structures Configuration Management is critical for testing Tests must be estimated, monitored and controlled Incidents need to be managed Standards for testing: quality, industry, testing Test Management 1 2 4 5 3 6 ISTQB / ISEB Foundation Exam Practice