1/15
Looks like no tags are added yet.
FL-5.1.1 (K2) Exemplify the purpose and content of a test plan
Test plan: documents means and schedule for planning, ensures perofrmed activities will meet established criteria, mean of communication with stakeholders, demonstrates that testing will follow defined test strategy and policy or explan why it will deviate
Test planning guides testers’ thinking to confront future challanges and risks
Test plan includes: context of testing (scope, test objectives, constraints)
Assumptiosn and constraints
Stakeholders (roles, responsibilities
Communication (form and frequency, documents)
Risk register
Test approach (levels, techniques, deliverables, entry/exit criteria, metrics, deviations from test policy)
Budget and schedule
FL-5.1.2 (K1) Recognize how a tester adds value to iteration and release planning
Release planning - write testable user stories and ACs, participate in project and quality risk analysis, estimate test effort for user stories, determie test approach
Iteration planning - detailed risk anylsis of user stories, break down user stories into tasks, estimate effort, identify funtional and non-functional aspects
FL-5.1.3 (K2) Compare and contrast entry criteria and exit criteria
Entry criteria - preconditions to start activity (if not met activity will be difficult and risky to conduct)
Exit criteria - what should be done to declare an activity completed
Entry and exit criteria should be defined for each level
Enry criteria includes: availability of resources and testware, initial quality level of test object
Excit criteria include: measures of thoroughtness (level of coverage, number of unfixed bugs, defect density), completion criteria(planned tests are executed, all found defects are reported)
Running out of budget and tume can be an exit criteria if ctakeholders accepted the risk
In Agile entry criteria - definiton of ready, exit criteria - definiton of done
FL-5.1.4 (K3) Use estimation techniques to calculate the required test effort
Estimation is a prediction of efforts needed to complete the task
Stakeholders should be aware about estimation error
Estimation techniques:
Estimation based on ratios: ratio between deveoopment and test effort is calculate based on previous projects info (e.g. 3:2). Current project development estimation is taken and testing estimation is calculated based on ratio
Extrapolation: velocity based. Historical data from this project is taken and average value is calculated
Wideband Delhi: expert-based. Experts make estimations in isolation, if there’re deviations in results, discussion is held and new round of estimation is taken (e.g. Plannning Poker in Agile)
Three-point estimation - experts give 3 estimations
a - optimistic estimation
m - most likely estimation
b - pessimistic estimation
Estimation is calculated with the formula: E = (a + 4m + b) / 6
Measurement error is calculated too SD = (b - a) /6
FL-5.1.5 (K3) Apply test case prioritization
Prioritization strategies:
Risk-based: test cases covering the most important risks are covered first
Coverage-based: test cases achieving highest coverage are executed first. Another variant - additonal coverage: 1st test case had the biggest coverage, next test case has the biggest amount of unique additional test cases
Requirements-based: the order on based on priorities or requirements, first cover most important
First cover dependencies, then priorities
Both technical and logical dependencies are equally important
FL-5.1.6 (K1) Recall the concepts of the test pyramid
Test pyramid shows that diffetent goals are supported by different levels of test automation
The higher the level, the lower granularity, slower and provide higher coverage
Levels:
UI (e2e)
Service (integration)
Unit (Component)
FL-5.1.7 (K2) Summarize the testing quadrants and their relationships with test levels and test types
Used to ensure that all appropriate teat types and test levels are included in SDLC
Q1 (technlogy facing, support the team) - component, component integration tests. Should be automated
Q2 (business facing, support the team) - fuctional, regression, user story, test cases, prototypes, API, simulations. Can be manual or automated
Q3 (business facing, critique the product) - exploratory, usability, acceprance. Manual testing
Q4 (technolofy facing, critique the product) - smoke, non functional (except usabilty). Automated tests
FL-5.2.1 (K1) Identify risk level by using risk likelihood and risk impact
Risk level consists of risk likehood and impact (harm)
Risk likehood - probability of the risk
Risk impact - consequences of risk occurence
FL-5.2.2 (K2) Distinguish between project risks and product risks
Project risks are process oriented, they are related to management and control of the project
e.g. delays, people issues, technical issue (poor requirements), supplier ieeus
Product risks are related to product quality characteristics
e.g. missing functionality, incorrect calculcation, runtime errors, poor architecture (affects non-functional requirements), inadequate response time, security vunerabilities
As a result users can be dissatisfied, lost of revenue or repitation, damage to third parties, high maintenance cost, criminal penalties, physical damage
FL-5.2.3 (K2) Explain how product risk analysis may influence thoroughness and scope of testing
Provide awareness to focus testing efforts in a way that minimizes level of the risk
Analysis includes risk identification and assessment
Risk identification (brainstorming, workshops, interviews, cause-defect diagrams)
Risk assessment (categorization of identifies risks, define risk likehood, impact and level, prioritize)
Product rirsk are used to: determine scope of testing (to include rirsk), determine test level and types, determine test techniques, estimate test effort, prioritize testing to find critical defects as early as possible, define activities that can be taken to reduce risk
FL-5.2.4 (K2) Explain what measures can be taken in response to analyzed product risks
Risk control includes risk minigation and monitoring
Risk mitigation - implementing actions to reduce risk level (risk mitigation by testing, risk acceptance, risk transfer, contigency plan - what to do whn the risk occurs if we accept it
Risk monitoring - ensure that taken acrions are effective, obtain firther info, identify emerging risks
Mitigation actions include: select testers with appropriate skills, apply needed level of independence of testing, conduct reviews,