Please enable JavaScript.
Coggle requires JavaScript to display documents.
5. Test Management - Coggle Diagram
5. Test Management
Test Planning
Purpose and Content of a Test Plan:
- Context of of testing (scope, test objectives, test basis)
- Assumptions and constraints (time and resources)
- Stakeholders (roles, responsibilities, hiring and training needs)
- Communication (forms and frequency of communication, documentation templates)
- Risk register (product risk, project risk)
- Test Approach (test levels, test types, test techniques, test deliverables, entry and exit criteria, independence of testing, metrics, test data and environment requirements, deviations)
- Budget and schedule
-
-
Estimation Techniques
Test effort estimation involves predicting the amount of test-related work needed to meet the objectives
Metrics-based
Based on historical of similar project or typical values
- Estimation based on ratios: are collected from previous projects, similar projects
- Extrapolation: measurements are made as early as possible in the current project to gather the data
Expert-based
Wisdom (predict) by owner or expert (TM or PM)
- Wideband Delphi
- Three-point estimation: are made by the experts:
-- the most optimistic estimation (a)
-- the most likely estimation (m)
- the most pessimistic estimation (b)
-- the final estimate: E = (a + 4*m + b)/6
Test case Prioritization
Test case Prioritization strategies:
- Risk-based prioritization: the most important risks are executed first
- Coverage-based : testcases with the highest coverage are executed first
- Requirements-based prioritization: based on the priorities of the requirements traced back to the corresponding test cases
Test Pyramid
- is model showing that different tests may have different granularity
- Order from bottom to top layer:
Unit test -> Service/Integration -> UI
- The higher layer <--> the lower the test granularity, test isolation and slower test execution time
Testing Quadrants
Group the test levels with the appropriate test types, activities, test techniques and work products in the Agile software development
Q1, Q2 tested by testing team
Q1:
- technical facing, support the team
-- UT, IT
-- should be automated
Q2:
- business facing, support the team
-- contains functional tests, user experience prototypes, API testing and simulations
-- check acceptance criteria
Q3, Q4 tested by user
Q3:
- business facing, critique the product
-- contains exploratory testing, usability testing and user acceptance testing
-- user-oriented and often manual
Q4:
- technical facing, critique the product
-- contains smoke tests and non-functional tests (except usability tests)
-- often automated
Risk Management
Risk definition and Risk Attributes
- Risk is a potential event, hazard, threat or situation whose occurrence causes an adverse effect
- Risk level = likelihood (probability) * impact (harm)
-
Risk analysis and control
- Allow the organization to
-- increase the likelihood of achieving objectives
-- improve the quality of their products
-- increase the stakeholder's confidence and trust
Risk analysis
- Risk identification: What are the risks?
- Risk assessment: likelihood and impact
Risk control
- risk mitigation: action to reduce impact of risk
- risk monitoring: compare actual and plan
Test Monitoring, Test Control and Test Completion
Metrics used in testing
- Test metrics are gathered to show:
-- progress against the planned schedule and budget
-- the current quality
-- the effectiveness
-- the approach
Common test metrics:
Project progress metrics
- task completion
- resource usage
- test effort
Test progress metrics
- test case status
- test environment preparing
- test execution time
Product quality metrics
- availability
- response time
- mean time to failure
Defect metrics
- number or priority of defects found/fixed
- defect density
-
Coverage metrics
- requirement coverage
- code coverage
-
Config Management
provides a discipline (integrity) for identify, controlling and tracking work products
- tracking and controlling the changes in the software
-