Chapter 5: Test Management Flashcards
What are the Tasks of a Test Manager?
Develop or review a test policy and test strategy for the organization Plan the test activities by considering the context, and understanding the test objectives and
risks. This may include selecting test approaches, estimating test time, effort and cost, acquiring
resources, defining test levels and test cycles, and planning defect management Write and update the test plan(s) Coordinate the test plan(s) with project managers, product owners, and others Share testing perspectives with other project activities, such as integration planning Initiate the analysis, design, implementation, and execution of tests, monitor test progress and
results, and check the status of exit criteria (or definition of done) and facilitate test completion
activities Prepare and deliver test progress reports and test summary reports based on the information
gathered Adapt planning based on test results and progress (sometimes documented in test progress
reports, and/or in test summary reports for other testing already completed on the project) and
take any actions necessary for test control Support setting up the defect management system and adequate configuration management of
testware Introduce suitable metrics for measuring test progress and evaluating the quality of the testing
and the product Support the selection and implementation of tools to support the test process, including
recommending the budget for tool selection (and possibly purchase and/or support), allocating
time and effort for pilot projects, and providing continuing support in the use of the tool(s) Decide about the implementation of test environment(s) Promote and advocate the testers, the test team, and the test profession within the organization Develop the skills and careers of testers (e.g., through training plans, performance evaluations,
coaching, etc.)
The way in which the test manager role is
What are the Tasks of a Tester?
Review and contribute to test plans Analyze, review, and assess requirements, user stories and acceptance criteria, specifications,
and models for testability (i.e., the test basis) Identify and document test conditions, and capture traceability between test cases, test
conditions, and the test basis Design, set up, and verify test environment(s), often coordinating with system administration and
network management Design and implement test cases and test procedures Prepare and acquire test data Create the detailed test execution schedule Execute tests, evaluate the results, and document deviations from expected results Use appropriate tools to facilitate the test process Automate tests as needed (may be supported by a developer or a test automation expert) Evaluate non-functional characteristics such as performance efficiency, reliability, usability,
security, compatibility, and portability Review tests developed by others
What are the Test Strategy and Test Approaches?
Analytical: This type of test strategy is based on an analysis of some factor (e.g., requirement or
risk). Risk-based testing is an example of an analytical approach
Model-Based: In this type of test strategy, tests are designed based on some model of some
required aspect of the product, such as a function, a business process, an internal structure, or a
non-functional characteristic (e.g., reliability). include business process models, state models, and reliability growth models.
Methodical: This type of test strategy relies on making systematic use of some predefined set of
tests or test conditions, such as a taxonomy of common or likely types of failures
Process-compliant (or standard-compliant): This type of test strategy involves analyzing,
designing, and implementing tests based on external rules and standards, such as those
specified by industry-specific standards, by process documentation, by the rigorous identification
and use of the test basis, or by any process or standard imposed on or by the organization.
Directed (or consultative): This type of test strategy is driven primarily by the advice, guidance, or
instructions of stakeholders, business domain experts, or technology experts, who may be
outside the test team or outside the organization itself. Regression-averse: This type of test strategy is motivated by a desire to avoid regression of
existing capabilities. This test strategy includes reuse of existing testware (especially test cases
and test data), extensive automation of regression tests, and standard test suites.
Reactive: In this type of test strategy, testing is reactive to the component or system being
tested, and the events occurring during test execution, rather than being pre-planned
What does the Typical entry criteria include?
Availability of testable requirements, user stories, and/or models (e.g., when following a modelbased testing strategy)
Availability of test items that have met the exit criteria for any prior test levels
Availability of test environment
Availability of necessary test tools
Availability of test data and other necessary resources
Typical exit criteria include:
What the Typical exit criteria include?
Planned tests have been executed
A defined level of coverage (e.g., of requirements, user stories, acceptance criteria, risks, code)
has been achieved The number of unresolved defects is within an agreed limit The number of estimated remaining defects is sufficiently low The evaluated levels of reliability, performance efficiency, usability, security, and other relevant
quality characteristics are sufficient
What are the Factors Influencing the Test Effort?
Product characteristics
The risks associated with the product The quality of the test basis
The size of the product
The complexity of the product domain
The requirements for quality characteristics (e.g., security, reliability)
The required level of detail for test documentation
Requirements for legal and regulatory compliance
Development process characteristics
The stability and maturity of the organization
The development model in use
The test approach
The tools used
The test process
Time pressure
People characteristics
The skills and experience of the people involved
Team cohesion and leadership
Test results
The number and severity of defects found The amount of rework required
What are the Test Estimation Techniques?
The metrics-based technique: estimating the test effort based on metrics of former similar
projects, or based on typical values The expert-based technique: estimating the test effort based on the experience of the owners of
the testing tasks or by experts
What is the Test Monitoring and Control scope?
The purpose of test monitoring is to gather information and provide feedback and visibility about test
activities.
What Fo Test Metrics assess?
Progress against the planned schedule and budget
Current quality of the test object
Adequacy of the test approach
Effectiveness of the test activities with respect to the objectives
What does a Typical test summary reports?
Summary of testing performed
Information on what occurred during a test period
Deviations from plan, including deviations in schedule, duration, or effort of test activities
Status of testing and product quality with respect to the exit criteria or definition of done
Factors that have blocked or continue to block progress
Metrics of defects, test cases, test coverage, activity progress, and resource consumption. (e.g.,
as described in 5.3.1)
Residual risks (see section 5.5) Reusable test work products produced
What are the Product and Project Risks ?
Project issues: o Delays may occur in delivery, task completion, or satisfaction of exit criteria or definition
of done o Inaccurate estimates, reallocation of funds to higher priority projects, or general costcutting across the organization may result in inadequate funding o Late changes may result in substantial re-work Organizational issues: o Skills, training, and staff may not be sufficient o Personnel issues may cause conflict and problems o Users, business staff, or subject matter experts may not be available due to conflicting
business priorities Political issues: o Testers may not communicate their needs and/or the test results adequately o Developers and/or testers may fail to follow up on information found in testing and
reviews (e.g., not improving development and testing practices) o There may be an improper attitude toward, or expectations of, testing (e.g., not
appreciating the value of finding defects during testing) Technical issues: o Requirements may not be defined well enough o The requirements may not be met, given existing constraints o The test environment may not be ready on time o Data conversion, migration planning, and their tool support may be late o Weaknesses in the development process may impact the consistency or quality of project
work products such as design, code, configuration, test data, and test cases o Poor defect management and similar problems may result in accumulated defects and
other technical debt Supplier issues: o A third party may fail to deliver a necessary product or service, or go bankrupt o Contractual issues may cause problems to the project
