Please enable JavaScript.
Coggle requires JavaScript to display documents.
ISTQB - Chapter 5 - Coggle Diagram
ISTQB - Chapter 5
-
Testing quadrants
- Group test levels with appropriate test types, activities, techniques, work products in Agile
- Include developer, tester, business representatives
- Tests can be business facing or technology facing
Q1: technology facing, support team
- component, integration test, should auto, CI
Q2: business facing, support team
- function, US, experience prototypes, API test, simulation
- manual/automated
Q3: business facing, critique product
- exploratory, usability, UAT
- often manual
Q4: technology facing, critique product
- smoke test, non-functional test (- usability)
- automated
Risk Management
- Potential event, hazard, threat, situation cause an adverse effect
- Risk likelihood: probability
- Risk impact: consequences
Product Risks
- related to product quality characteristic (ISO 25010)
Project Risks
- related to management and control project
- organization, people, technical, supplier... issues
Estimate Techniques
Metrics-based techniques:
- base on metrics of former(old) similar projects/ typical values
Estimate based on ratios
- derive standard ratios for similar projects
- take form historical data
Extrapolation (ngoai suy)
- Extrapolate data
- Extrapolate test effort as the averaged from last 3 iterations
Expert-based:
- base on experience of the experts
-
Three-point estimation
- E = (a + 4m+b)/6
a: the most optimistic
b: the most likely estimation
c: the most pessimistic
SD = (b-a)/6
Test Leader vs Tester
Test Leader:
- Plan, policy, strategy, test approach, time, effort, cost, resource, exit criteria...
- Initiate, monitor, facilitate, adapt, control, report
- Support select/setup management tools, testware,metrics
- Decide, promote, develop careers of testers
Tester
- Review, analyze, assess, identify, design, set up, verify,
- prepare, create, execute, evaluate results...
Test Report
Test progress reports
- Support ongoing control and provide information to modify test schedule, resources, test plan when needed
Test completion reports:
- Summarize a specific stage of testing
Test Plan
- Decribes objective, resource, process...
- Ensure test activities meet the criteria
- Demonstrate that test adhere test policy and test strategy
- Force tester contfront risks, schedules, tools, costs, effort..
- Include: context, assumptions and constraints, stakholders, communication, risks, test approach: test type, test level. techniques, entry - exit criteria, budget, schedules
-
Test case Prioritization
- Test execution schedule, order
- Risk-based, coverage-based, requirement-based
- Dependencies, availability of resources (test tool, environment, time...)
-
-
