ISTQB – Test Manager

1. ISTQB – Test Manager Ramona Baleti Tabara de Testare - 20 septembrie 2012

2. Cuprins • Documente de parcurs • Rolul unui test manager • Despre examen • Capitole • Informatii utile

3. Documente de parcurs • Rex Black - “ ISTQB Advanced Test Manager.pdf” • “ IEEE Std 829 “ - for Software Test Documentation • “ IEEE 1028 - reviews standard “ • “ British Testing Std - Component Testing “ • Anne Mette - “ Guide to advanced Software Testing” • Rex Black - “ Critical Testing Processes Plan, Prepare, Perform, Perfect “ • R.Craig, S.Jaskiel -“ Systematic.Software.Testing “ • Judy McKay - “ Managing the Test People “ • Ilene Burnstein - “ Practical Software Testing “

4. Rolul unui test manager • Define the overall testing goals and strategy for the systems being tested • Plan, schedule, and track the tasks • Describe and organize the necessary activities • Select, acquire, and assign the adequate resources to the tasks • Select, organize, and lead testing teams • Organize the communication between the members of the testing teams and between the testing teams and all the other stakeholders • Justify the decisions and provide adequate reporting information where applicable

5. Despre examen - obiective "Not everyone who doesn't study for the exam will fail. But everyone who does fail didn't study enough." A frequent warning from the author when teaching ISTQB courses. • Level 1: Remember (K1) • Level 2: Understand(K2) • Level 3 : Apply(K3) • Level 4: Analyze(K4) • K1: The candidates will recognize, remember and recall a term or concept. • K2: The candidates can select the reasons or explanations for statements related to the topic. They can summarize, compare, classify and give examples for concepts of testing. • K3: The candidates can select the correct application of a concept or techniques and/or apply it to a given context. • K4:The candidate can separate information related to a concept or technique into its constituent parts for better understanding, and can distinguish between facts and inferences.

6. Despre examen - desfasurare 65 questions: • •Multiple choice • •Scenario-based questions Structure: • (65 questions) • 30 K2 each 1 point • 14 K3 each 2 points • 21 K4 each 2 points 3 hours Score >= 65% pointsto pass

7. Capitole • Basic aspects of software testing • Testing processes • Test management • Test techniques • Testing of software characteristics • Reviews • Incident (defect) management • Standards and test process improvement • Test tools and automation • People skills (team composition)

8. 1. Basic aspects of software testing • Testing in the software lifecycle • Lifecycles – sequential, iterative, spiral • Specific systems Systems of systems - independent systems tied together to serve a common purpose Safety-Critical systems - are those systems upon which lives depend • Metrics and measures for testing and quality • Ethics • Testing in the software lifecycle • Lifecycles – sequential, iterative, spiral • Specific systems Systems of systems - independent systems tied together to serve a common purpose Safety-Critical systems - are those systems upon which lives depend • Metrics and measures for testing and quality • Ethics Foundation Foundation

9. 2. Testing processes Drill Sergeant:Gump! Why did you put that weapon together so quickly, Gump? Forrest Gump:You told me to, Drill Sergeant? Drill Sergeant: [Expressing surprise and looking at a stopwatch.] This is a new company record! If it wouldn't be such a waste of a fine enlisted man, I'd recommend you for OCS! You are gonna be a general some day, Gump. Now disassemble your weapon and continue! —Forrest Gump displays an innate ability to follow a process accurately and quickly in a scene the movie Forrest Gump.

10. 2. Testing processes process activities: • Planning and control • Analysis and design • Implementation and execution • Evaluating exit criteria and reporting • Test closure activities

11. 3. Test management Risk-Based Testing product risk: A risk directly related to the test object. project risk: A risk related to management and control of the (test) project, e.g., lack of staffing, strict deadlines, changing requirements, etc. risk: A factor that could result in future negative consequences; usually expressed as impact and likelihood.

12. 3. Test management Failure Mode and Effect Analysis (FMEA) A systematic approach to risk identification and analysis in which you identify possible modes of failure and attempt to prevent their occurrence. - most formaltechnique for risk-based testing - consider it for high-risk or conservative projects

13. 3. Test management • Test Management Documentation • Test Estimation • Scheduling Test Planning Dwight Eisenhower, United States general and president, once said,"In preparing for battle I have always found that plans are useless, but planning is indispensable." • Test Progress Monitoring and Control • Business Value of Testing • Distributed, Outsourced, and Insourced Testing • Test Management Issues

14. Capitolele 4 si 5 4. Test Techniques – test design techniques: specification based, structure based, defect based, experienced based 5. Testing of software characteristics -quality attributes: accuracy, suitability, usability, accessibility, reliability, maintainability, portability etc. From Foundation

15. 6. Reviews • review: An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, informal review, technical review, inspection, and walkthrough. • reviewer: The person involved in the review that identifies and describes anomalies in the product or project under review.

16. 7. Incident (defect) management • defect (or bug): A flaw in a component or system that can cause the component or system to fail to perform its required function • error: A human action that produces an incorrect result. • failure: Deviation of the component or system from its expected delivery, service, or result. • incident: Any event occurring that requires investigation. • incident logging: Recording the details of any incident that occurred, e.g., during testing.

17. 7. Incident (defect) management

18. 8. Standards and test process improvement test process improvement models: • Critical Testing Processes (CTP) • Systematic Test and Evaluation Process (STEP) • Test Maturity Model (TMM) • Test Process Improvement (TPI) (TMM): A five-level staged framework for test process improvement, related to the Capability Maturity Model (CMM), that describes the key elements of an effective test process. (TPI): A continuous framework for test process improvement that describes the key elements of an effective test process, especially targeted at system testing and acceptance testing.

19. 9. Test tools and automation "What is the business case for automation?" —A question posed by the author to a team of consultants who had been working for a client for four years without making significant progress in the percentage of test cases automated. They were unable to answer the question in any meaningful fashion. • Test Management Tools, Test Execution Tools, Keyword-Driven Automated Test Execution…

20. 10. People skills (team composition) As test managers, we need to motivate our team members… How? • Recognition • Management approval • Respect • Adequate rewards

21. Informatii utile Accent pe: • Chapter 3. Test Management • Chapter 10. People Skills and Team Composition La examen am avut intrebari despre: • RAD - Chapter 1. Test Basics • TMM(Test Maturity Model), TPI(Test Process Improvement) - Chapter 8. Standards and Test ProcessImprovement • test strategy - Chapter 3. Test Management • FMEA(Failure Mode and Effect Analysis) - Chapter 3. Test Management • 3 intrebari au fost ca in cartea lui Rex Black

22. Informatii utile • Loc pentru sustinere in Timisoara: Test Centre Location About Training and Consulting Str. Ludwig von Ybli nr.36, et.I About Business Center Timisoara 30069-3 Romania  Colaborare cu ISQI GmbH (International Software Quality Institute) – Potsdam Germany

23. Va multumesc pentru atentie!