Workshop on testing risks - course RUB 9,500. from IBS Training Center, training 8 hours, Date November 26, 2023.

Topics covered:
1. Project preparation:
Incomplete assessment of labor costs;
Testing work schedule;
Incomplete scope testing;
Ignoring internal testing risks.
2. Testing strategy:
There is no testing strategy;
Test strategy is not supported;
Working with requirements (using Agile as an example);
Scope of testing (using Agile as an example);
Scope of testing (using the example of an iterative model);
Criteria for starting and completing testing;
Risks of testing.
3. Requirements analysis:
Requirements are analyzed and developed without the participation of testers;
Requirements change without the participation of testers;
Requirements are not prioritized;
There are no requirements in the project;

Requirements are constantly changing;
No analyst – no one to support the requirements;
4. Design:
System architecture is not taken into account when developing a testing strategy;
Requirements are replaced by design specifications;
There is no single solution for user interfaces;
The test object does not have a user interface
There are no requirements for the system environment.
5. Test plan:
Coverage of requirements by test scenarios is not analyzed;
Assessing the quality of the test plan during the development process;
Assessing the quality of the test plan during application;
There are no plans to review the test plan;
There is no review of the test plan;
Interaction and order of application of various test plans;
Test cases do not contain details;
Test cases contain details;
Design and development of test data is not planned or performed.
6. Test automation:
Functional testing automation is applicable to any project;
Functional test automation is only applicable to regression testing;
Functional testing automation is only applicable when there are a large number of testing rounds;
Early load testing;
Inadequate load model.
7. Test environment:
Testing is performed in the development environment;
Same testing environment for multiple projects.
8. Testing:
Testing is not carried out as planned;
Defects found outside the test plan do not lead to its adjustment;
Testing deadlines are not met;
There are not enough testing resources;
The version of the test object cannot be identified;
The test object is not operational;
Defects occur due to incorrect configuration of the system/testing environment;
Testing protocols are not created;
How to write a defect description;
Testing metrics are not used;
Communication and correction of defects “on the fly”;
Hiding defects;
User documentation is not tested;
No system testing is carried out.
9. Acceptance:
The acceptance procedure has not been agreed upon;
Verification and validation;
Acceptance testing plan;
Acceptance testing schedule;
Customer expectations;
Decision maker.