1. Testing Process
Roman Yagodka
ISS Test Leader

2. Contents Introduction Simplified Project Lifecycle Model
Main Project Stages

3. Introduction
Testing (as a function of Quality Control) is a necessary part of software development process
Test group must be involved at the every stage of development process, not only at the System Testing phase
While working closely with developers, test group shall be as much independent as possible

4. Simple Project Lifecycle Model
- Project Kick-off
- Requirements gathering
- Planning
- Closure
- Postmortem
- Functional specs
- Test Framework
- Test Development
well…
Req. & Planning
Design
Coding
Testing
Release
Time

5. Project Kick-off
It is the very first team meeting before starting the project
Outputs:
Project definition (objectives, outputs/products)
Team (team members, organisation, training needs)
High level plan
Detailed plan for the next stage
Req. & Planning

6. Project Kick-off (cont.)
Overview of what is need to be tested
Comments, Advises and Recommendations about testing activities
Customer (if available)
Developers
Testers
Preliminary schedule for the nearest steps in Testing
Req. & Planning

7. Requirements Gathering
Process of collecting high-level requirements from customer and/or end-users.
Output:
Requirement Book is approved by customer (if any)
Req. & Planning

8. Requirements Gathering (cont.)
Test team tasks:
Check requirements for completeness, consistency and unambiguity (usually done during review)
Consider tools and technologies needs
Req. & Planning

9. Planning Project Management Plan Quality Assurance Plan
Configuration Management Plan
Test Plan
Req. & Planning

10. Planning (cont.) Test Plan includes: Approach Features to be tested
Features not to be tested
Testing priorities
Estimations
Environmental needs
Req. & Planning

11. Functional Specifications
Functional specifications (FS) are based on high-level requirements from Requirements Book
It is the basis for further test development and testing
Test team tasks:
Check FS requirements for completeness, consistency and unambiguity
Check requirements for testability
Revise and update testing plans, if necessary
Design

12. Test Framework
Intended for automated testing support, whether of GUI or non-GUI applications
Responsibility of the Test Leader and/or senior testers
Output:
Test Framework
Test Procedure document
Design

13. Test Development
Testers may co-operate with developers, retrieve prototypes and intermediate builds for test development and correction
Informal System testing may be conducted at already implemented functionality
Output:
Test Cases
FS-to-Test traceability
Coding

14. System Testing Testing: Cycles: Non-stop
Divided into cycles (build->test->correct->build)
Cycles:
Formal – all tests are executed to verify all features
Informal – partial testing is allowed
Testing

15. Closure Final Test Cycle Test Report This is a formal test cycle
Before the Final Test Cycle defects trend shall show readiness to final testing
No critical defects shall be found at the Final Cycle, otherwise release is postponed
All low-severity defects are postponed and workarounds are described in user documentation
Test Report
Release

16. Post mortem
Post mortem is a project team meeting with the main goal to review the successes and failures of the past project
Post mortem report may be used to remind good and bad practices before starting a new project
Testers should focus on the following items:
Estimations accuracy (defects and test cases count)
Test Automation
Communication
Release

17. Conclusion The process gives the following advantages:
Tracking and quantitative measurement ability;
Decreasing human factor;
Results repetition;
Continuous process improvements ability.

18. The End Thank You For Attention