![3 Steps to Smart Delegation [Time Management Series]](https://rogeriodasilva.com/wp-content/uploads/2020/12/Three-steps-to-Smart-delegation-and-why-everyone-should-be-delegating.jpg)
![7 Areas to Improve Your Productivity in the New Year [2022]](https://rogeriodasilva.com/wp-content/uploads/2020/01/defect-tracking-tool-software-bug-pexels-kevin-ku-577585-150x150.webp){kind=tracking}
Fundamental Test Process
Basics for test process on an everyday basis. Ideal for giving you a higher level idea of what a software tester does.
Ideal for a Junior Software Tester or who is intended to take the ISTQB-ISEB exam.
Fundamental Test Process
Download the High-Resolution image. (PNG format)
Download the A3 size to print in that size. (PDF format)
I have shared this mind map. Copy it away and amend it as you like.
Fundamental Test Process
1. Planning & Control
Planning
- Determine the scope, risks & objectives.
- Implement Test Policy / Strategy.
- Determine Test Approach.
- Determine resources required.
- Schedule the test activities.
- Determine the Exit Criteria.
Control
- Monitor activities.
- Compare progress vs plan.
- Take control when required.
2. Analysis & Design
- Review the Test Basis.
- Eval Test Basis for test-ability.
- Identify & priorities Test Conditions.
- Design & priorities high-level Test Cases.
- Identify Test Data.
- Trace-ability between Test Bases & Test Condition.
- Test environment & Infrastructure tools.
3. Implementation & Execution
Test Implementation
- Finalise, Implement & prioritise Test Cases.
- Create Test Data.
- Check environment ready.
- Create Test Suites.
- Develop & priorities Test Procedures.
- Test harness / automated scripts (optional).
Test Execution
- Execute Test Procedure as planned.
- Log the outcome.
- Compare actual vs expected.
- Report discrepancies as Incidents.
- Analyse Incidents for cause.
- Retest / Regression.
4. Evaluating Exit Criteria & Reporting
- Check logs against Exit Criteria.
- Assess if more tests are needed or Exit Criteria need to be changed.
- Write Test Summary Report for stakeholders.
5. Test Closure
- Check planned deliverables.
- Close Incident Reports.
- Handover to maintenance.
- Finalise & archive test-ware / environment.
- Document acceptance of a system.
- Analyse lessons learned for future projects & improve test maturity.
Tools I’ve used to help with the video and mind mapping:
Mind Mapping – Mindmeister
Plan and brainstorm online with friends with the free mind-mapping tool MindMeister.
What it says in ISTQB
Full Training
- ISTQB Foundation Level 2011 Training 1st Month Free*.
- ISTQB Foundation Leve 2018 Training – Coming Soon | YouTube Preview
References:
en.wikipedia.org/wiki/Software_test_documentation
www.computing.dcu.ie/~davids/courses/CA267/ieee829mtp.pdf
standards.ieee.org/findstds/standard/829-2008.html
www.ufjf.br/eduardo_barrere/files/2011/06/SQETestIncidentReportTemplate.pdf
