1 / 26

PUTTING THEORY INTO PRACTICE: TEST TEAM LEADER

PUTTING THEORY INTO PRACTICE: TEST TEAM LEADER Planning, estimating, scheduling and progressing testing work A TWO DAY WORKSHOP BY GEOFF QUENTIN. Administration. Orange form Name card Personal objectives. PUTTING THEORY INTO PRACTICE: TEST TEAM LEADER. The philosophy

johannes-jesse
Download Presentation

PUTTING THEORY INTO PRACTICE: TEST TEAM LEADER

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PUTTING THEORY INTO PRACTICE: TEST TEAM LEADER Planning, estimating, scheduling and progressing testing work A TWO DAY WORKSHOP BY GEOFF QUENTIN

  2. Administration • Orange form • Name card • Personal objectives

  3. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • The philosophy • Theory is necessary • Practical is where one learns the real work • Support during learning is vital • Material to take away is vital • Continuing to learn after the course is vital

  4. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • Your presenter • Experience • Career support • Contact point from now on

  5. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER Contents of this two day workshop 1. Introduction 2. Planning 3. Estimating 4. Scheduling 5. Progressing the work supported by exercises, briefing notes and other materials

  6. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • Timetable - Day 1 • Morning • introduction • planning • Afternoon • estimating • Start 9:00 close at 17:00 • Lunch 12:30 - 13:30 • Other breaks as needed just like a normal working day

  7. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • Timetable - Day 2 • Morning • scheduling • Afternoon • progressing • the way forward • Start 9:00 close at 17:00 • Lunch 12:30 - 13:30 • Other breaks as needed just like a normal working day

  8. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • The format of the course • Theory 20% • Practical 80% • How to learn: • Learning by doing • Your own work • Team work • Tutor led discussions and individual tuition • Management presentations as needed

  9. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • The Competency Award • The award • pass, merit, distinction (it is possible to fail) • Give you confidence to tackle similar work • The practical awards available from QBIT • Test Analyst • Test Team Leader • Test Manger • These are to complement the theoretical ISEB awards

  10. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • The case study • Online application • The role you play: • acquirer - user acceptance test plans • supplier/developer - system test plans • The role the presenter plays

  11. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • What you are expected to create • Test plan (system or acceptance) • list of test deliverables • Gantt chart with tasks and dependencies • Budget for resources required • Schedule of resources and work • Reports and reporting mechanism • Example work assignments

  12. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • Materials available for reference • Briefing notes • Copies of selected standards especially • IEEE 829 and ISO 12207 • Books • The Generic Test Process • Course material from • Planning for Testers • The work of other teams • Web sites

  13. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • The role of the professional tester • The skill set • planning, scheduling, analysing, designing, scheduling, executing and reporting • Material published in Professional Tester • eight part series; skills of the professional tester • Demands of industry • Other qualifications

  14. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • The QBIT GTP • Repeatable • Reportable • Applicable • Adaptable

  15. QBIT GTP PROJECT DOC SPEC 1. TEST STATUS REPORTING TEST STRATEGY 2. TEST STRATEGY TEST ITEM HIGH LEVEL TEST PLAN 3. TEST PLAN LOW LEVEL TEST PLAN LOW LEVEL TEST PLAN LOW LEVEL TEST PLAN LOW LEVEL TEST PLAN TEST OBJECTIVES LIST 4. TEST ANALYSIS 5. TEST DESIGN TEST SCRIPT 6. TEST SCHEDULING TEST SCHEDULE TEST ITEM TRANSMITTAL REPORT TEST EXECUTION TEST LOG TEST ITEM TRANSMITTAL REPORT TEST INCIDENT REPORT 7. TEST EXECUTION TEST SUMMARY REPORT

  16. 1. TEST STATUS REPORTING 2. TEST STRATEGY 3. TEST PLAN 4. TEST ANALYSIS PTP - 3 PTP - 2 PTP - 1 5. TEST DESIGN 6. TEST SCHEDULING 7. TEST EXECUTION The generic test process The PTP series of courses PTP 1 – Test Analysis, design and execution PTP 2 – Test planning and scheduling PTP 3 – Test status reporting and test strategy

  17. Specific study PROJECT DOC SPEC 1. TEST STATUS REPORTING TEST STRATEGY 2. TEST STRATEGY TEST ITEM HIGH LEVEL TEST PLAN 3. TEST PLAN LOW LEVEL TEST PLAN LOW LEVEL TEST PLAN LOW LEVEL TEST PLAN LOW LEVEL TEST PLAN TEST OBJECTIVES LIST 4. TEST ANALYSIS 5. TEST DESIGN TEST SCRIPT 6. TEST SCHEDULING TEST SCHEDULE TEST ITEM TRANSMITTAL REPORT TEST EXECUTION TEST LOG TEST ITEM TRANSMITTAL REPORT TEST INCIDENT REPORT 7. TEST EXECUTION TEST SUMMARY REPORT

  18. The low level test plan The relationship of the low level test plan to the project test strategy and plan Project test strategy Management level Specific test plans Project test plan UAT test plan System test plan Link test Plan Unit test plan

  19. The status indicators - 1 1 Test reference assigned 2 Business objectives identified Business objectives identified and Critical Success Indicator established Test strategy defined 3 Planned -test objects identified Planned -test objects identified and test objectives set Planned -test objects identified, test objectives set and prioritised 4 Analysed -attributes defined Analysed -criteria/conditions specified Analysed -criteria/conditions prioritised

  20. The status indicators - 2 5 Designed -method identified Designed -method identified and data created Designed -method,data and test procedure Designed -method,data,procedure,test environment and set up Designed -method,data,procedure,test environment and set up and checked 6 Scheduled -date assigned Scheduled -resources allocated Scheduled -pre-conditions met and test ready to run 7 Executed -re-test needed (because of re-work) Executed -re-test and regression test needed Executed -accept with qualifications Executed -accepted (test run)

  21. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • Revision of the review process • Universal • Widely applicable • Build it to your plans!

  22. Low level test plan TP-00 Test Script TS-00 Business Objective Test Object Test Objective Completion Criteria Test Method Test Data Test Set Up Test Schedule Test Execution Test Status Test Script TS-00 Business Objective Test Object Test Objective Completion Criteria Test Method Test Data Test Set Up Test Schedule Test Execution Test Status Test script TS-00 Business objective Test object Test objective Completion criteria Test method Test data Test set Up Test schedule Test execution Test status 2 Validation Business analysis Risk assessment Quality requirements System of change 3 Testing (Certification) What are we going to test and when Design or specification document Verification Complete? Consistent? Unambiguous? Accurate? Compliant? To Standard? A model of the review process The 123 review 1

  23. PUTTING THEORY INTO PRACTICE:TEST TEAM LEADER • Now to start the course • Select the role • user acceptance test team leader • supplier/developer system test team leader • Need to decide on management presentations • Arrange your work area

More Related