ISTQB Foundation - Chapter 5 - Test Management Questions And Answers Latest Updates

Project risks - ️️Supplier issues, skill or staff shortage, personal issues, requirement issues, test environments not ready, low quality of design, code, and tests Test leader tasks - ️️1) Coordinating the development of the test strategy and plan with project managers 2) Writing or reviewing test strategies 3) Contributing testing perspective to other project activities 4) Planning the development of the required tests 5) Taking required action on issues 6) Scheduling testing activities Risk - ️️a factor that could result in future negative consequences Level of risk - ️️Probability of risk occurring x impact if it did happen Product risks - ️️Failure prone software delivered, potential for a defect to cause harm, poor software characteristics, software that doesn't do what it is supposed to Risk-based testing - ️️Proactively reduces the risk by identifying them and mitigating them as soon as possible Risk-based approach - ️️1) Determines test techniqes and the extent of testing needed 2) Prioritize testing in an attempt to find critical defects as early as possible 3) Determines non-testing techniques that could reduce risk Test approach - ️️All of the decisions made on how testing should be implemented, based upon project goals and risk assessment Factors for selecting a test approach - ️️1) Risk of failure of the project 2) Skills and experience of the people in the proposed techniques, tools, and methods 3) Object and mission of the testing team 4) Regulatory aspects 5) Nature of the product and businessMaster test plan - ️️Main document produced in testing which details each of the other test plans IEEE 829 - ️️Standard for Software Test Documentation 16 sections of IEEE 829 - ️️S - scope P - people A - approach C - criteria E - environment needs D - deliverables (test) I - identifier and introduction R - risks and contingencies T - testing tasks and schedule Test planning activites - ️️1) Working with the project manager and SMEs to determine the scope and risks 2) Putting together the test strategy 3) Liaising with the project 4) Working with the project to decide what needs to be tested 5) Building a plan that identifies when and who will do the test analysis and design 6) Finding and assigning resources 7) Deciding what docs will be needed 8) Ensuring test documentation generates repeatable test assets Entry criteria - ️️Determines when a test activity can start Exit criteria - ️️Determines when a given test activity has been completed or when it should stop Two approaches of test estimation - ️️Metrics-based approach and expert-based approach Metrics-based approach test estimation - ️️Estimates the cost and time of a project based on metrics from previous or similar projects Expert-based approach test estimation - ️️Estimates the cost and time of a project based on the experiences of the task owners Test control - ️️The activity of using information from test reporting to decide on a course of action to ensure control of the test activities is maintained and exit criteria are met Risk - ️️a factor that could result in future negative consequencesLevel of risk - ️️Probability of risk occurring x impact if it did happen Project risks - ️️Supplier issues, skill or staff shortage, personal issues, requirement issues, test environments not ready, low quality of design, code, and tests Product risks - ️️Failure prone software delivered, potential for a defect to cause harm, poor software characteristics, software that doesn't do what it is supposed to Risk-based testing - ️️Proactively reduces the risk by identifying them and mitigating them as soon as possible Risk-based approach - ️️1) Determines test techniqes and the extent of testing needed 2) Prioritize testing in an attempt to find critical defects as early as possible 3) Determines non-testing techniques that could reduce risk Test leader tasks - ️️1) Coordinating the development of the test strategy and plan with project managers 2) Writing or reviewing test strategies 3) Contributing testing perspective to other project activities 4) Planning the development of the required tests 5) Taking required action on issues 6) Scheduling testing activities