Preparation stage
Determine and agree the test strategy of US
Determine the required testing levels for US
Consider Project / Product Risks
Heuristic Risk-Based Testing
PRISMA
Determine the scope of features which must be tested
Timing
We take into account the fact that the US can be resolved in the end of the iteration.
Determine the depth of testing, % of acceptable test coverage and exit criteria
For example, 60% for main functions and 40% for additional
Consider the role matrix
If it is on the product
Consider user configurations
According to the matrix of user platforms
Consider the interaction components matrix
We test the US
For example: Informal review
Determine the necessary Test Types for US
Functional
Non-functional (ISTQB)
Reliability testing
Usability testing
Efficiency testing
Maintainability testing
Portability testing
Baseline testing
Compliance testing
Documentation testing
Endurance testing
Load testing
Performance testing
Compatibility testing
Security testing
Scalability testing
Volume testing
Stress testing
Recovery testing
Internationalization testing and Localization testing
Take into account the requirements for the quality characteristics of the product
Analyze the new US functional
Input field: Date
Input Method
From the keyboard
From the buffer
Drag and Drop
Security
Different types of injections
Security of personal data/settings
Аccess according the Role model
A user with one role must not have the functions of another
Always Invalid Days
Feb 30, Sept 31, Feb 29 in Non-Leap Years
Different Formats
November 16, 2017; 16/11/2017; 16/11/17; 16-11-17
Different ways to write the date
day-month-year
month-day-year
Letters, special characters
Time Difference between Machines
Crossing Time Zones
Discuss the appropriate test-design techniques
Black Box Testing Techniques
Equivalence Class Testing
Boundary Value Testing
Combinatorial e.g.
Pairwise Testing
Orthogonal arrays
Decision Table Testing
State-Transition Testing
Domain Analysis Testing
Use Case Testing
Classification trees
Test Trees
Cause Effect graphing
...
White Box Testing Techniques
Control Flow Testing
Data Flow Testing
Experience-based
Error guessing
Exploratory Testing
Create a list of possible bugs by using Error guessing technique
Risk Analysis
We carry out an analysis of the new risks
We analyze the interaction of new and existing risks
We define the strategy of work with them
Analysis the interaction components matrix
We analyze how the new feature affects/ modifies the existing interaction components matrix
Correct it
Using Automation
Autotests
We analyze the US from the point of view of creating new autotests and changing of existing
Setup configurations
Create master data
Generating test cases
For Paiswise
For STT
...
Regression
We analyze the US from the point of view of creating new/modify regression test plan
Determine the test approach and the way of data storage
Script approach
Test cases
Acceptance test cases
Check-lists
Exploratory Testing
Make a team time assessment (poker)
Creating test cases
Working with Autotests
Non-functional testing
Functional testing
Preparation of test data, setting of environments