
IEEE-829-1998 – Standard for software Test Documentation
Key elements of IEEE-829-1998 – Standard for Software Test Documentation.
Provides an overview of the IEEE 829-1998 Standard for Software Test Documentation.
Ideal for Junior Testers who intend to take the ISTQB-ISEB exam.
IEEE 829-1998 Mind Map
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.
IEEE 829-1998 – Standard for Software Test Documentation
1. Test Plan
- Test Plan Identifier.
- Introduction.
- Test Items.
- Features to be Tested.
- Test Approach.
- Items Pass / Fail Criteria.
- Suspension Criteria & Resumption Requirements.
- Test Deliverables.
- Testing Tasks.
- Environmental Needs.
- Responsibilities.
- Staffing & Training Needs.
- Schedule.
- Risk & Contingencies.
- Approvals.
2. Test Design specification
- Test Conditions (Coverage Items).
- Detailed Approach.
- High-Level Test Cases.
3. Test Incident Report
- Report ID.
- Summary.
- Description.
- Impact.
4. Test Summary Report
- Summary.
- Variances.
- Comprehensiveness Assessment.
- Summary of Results.
- Evaluation.
- Summary of Activities.
5. Test Procedure / Script specification
- Purpose.
- Special Requirements.
- Procedure / Script Steps.
6. Test Case Specification
- Objectives.
- Preconditions.
- Input Specification.
- Output Specification.
- Post-conditions.
- Inter-case Dependencies.
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
It’s ironic how many typos are in this document.