ieee829-2008 Software Test Documentation Standard Introduction

A set of documents is defined in version 1998 for the 8 defined software testing phases:

Test plan: The documentation for a management plan includes:

How the test is done (including the configuration of the SUT).

Who's going to do the test?

What will be tested

How long the test will last (although it varies depending on the resource limits that can be used).

Test coverage requirements, such as the required quality level

Test design Specifications: Describe in detail the test environment and expected results, as well as the standards passed by the test.

Test Case Specification: Defines the test data used to run the conditions described in the test design specification.

Test process Specification: Describes in detail how each test is carried out, including each preset condition and next steps.

Test Item Delivery Report: Reports when the software components are tested from one test phase to the next test phase.

Test records: Records which test cases were run, who ran them, in what order, and whether each test item passed or failed.

Test additional reports: Describe in detail any failed test items, as well as the actual expected results corresponding to them, and other information designed to uncover why the test failed. This document is named as an additional report rather than an error report because there may be differences between the expected and actual results for some reason, which is not considered a system error. This includes errors in expectations, tests being executed incorrectly, or differences in understanding of requirements. This report consists of all of the following additional details, such as actual results and expected values, when failures, and other evidence to help solve the problem. This report may also include an assessment of the impact of this additional item on the test.

Test Summary Report: A management report that provides all important information that is not mentioned until the test is complete, including the evaluation of the test effect, the quality of the software system being tested, and the statistics from the test attached report. The report also includes what test items were executed and how long it took to improve the future test plan. This final report is intended to indicate whether the software system under test is consistent with the acceptable standards proposed by the project manager.

Master test Plan in ieee829-2008

The Master Test Plan (template)

1. Introduction
1.1. Document identifier
1.2. Scope
1.3. References
1.4. System Overview and key Features
1.5. Test Overview
1.5.1 Organization
1.5.2 Master Test Schedule
1.5.3 Integrity Level Schema
1.5.4 Resources Summary
1.5.5 Responsibilities
1.5.6 Tools, techniques, methods, and metrics

2. Details of the Master Test Plan
2.1. Test processes including definition of test levels
2.1.1 Process:management
2.1.2 Process:acquisition
2.1.3 Process:supply
2.1.4 Process:development
2.1.4.1 activity:concept
2.1.4.2 activity:requirements
2.1.4.3 activity:design
2.1.4.4 activity:implementation
2.1.4.5 Activity:test
2.1.4.6 Activity:installation/checkout
2.1.5 Process:operation
2.1.6 Process:maintenance
2.1.6.1 activity:maintenance Test
2.2. Test Documentation Requirements
2.3. Test Administration Requirements
2.4. Test Reporting requirements

3. General
3.1. Glossary
3.2. Document Change Procedures and history

The level Test Plan (template)

1. Introduction
1.1. Document identifier
1.2. Scope
1.3. References
1.4. Level in the overall sequence
1.5. Test classes and overall test conditions

2. Details for the level of test Plan
2.1 test items and their identifiers
2.2 test traceability Matrix
2.3 Feat Ures to is tested
2.4 Features not to be tested
2.5 approach
2.6 Item pass/fail criteria
2.7 suspension CR Iteria and resumption Requirements
2.8 Test Deliverables

3. Test Management
3.1 Planned activities and tasks; test progression
3.2 environment/infrastructure
3.3 responsi Bilities and Authority
3.4 Interfaces among the parties involved
3.5 Resources and their allocation
3.6 Traini Ng
3.7 Schedules, estimates, and costs
3.8 Risk (s) and contingency (s)

4. General
4.1 Quality assurance Procedures
4.2 Metrics
4.3 Test coverage
4.4 Glossary
4.5 Document Chang e Procedures and History

Other standards that may be referenced in IEEE 829

IEEE 1008, standard for unit testing
IEEE 1012, standard for software inspection and validation
IEEE 1028, standard for software inspection
IEEE 1044, standard for software exception classification
IEEE 1044-1, software exception classification guide
IEEE 1233, guidelines for developing software requirements specifications
IEEE 730, standard for software quality assurance programs
IEEE 1061, standard for software quality metrics and methodologies
IEEE 12207, a standard for software lifecycle processes and software life-cycle data
BSS 7925-1, Glossary of software testing terminology
BSS 7925-2, standard for software component testing

Due to the limited space, today first come here, hope that your software quality management can help. Other articles you might be interested in:

Web testing introduces a UI test
Web Test Introduction 21 Security Test
Software Testing Process Reference one
Ten free Web UI test tools
Design ideas of Internet database architecture
Enterprise Application Architecture mode N-tier multi-tier architecture
An enterprise social application network topology architecture diagram
IT Infrastructure planning scenario one (network system planning)
Food chain Company It informatization solution One
Rest Service Introduction
Enterprise Service Bus Introduction

If you want to know more software development, system it integration, Enterprise informatization, project management and other information, please follow my subscription number:

Petter Liu
Source: http://www.cnblogs.com/wintersun/
This article is copyright to the author and the blog Park, Welcome to reprint, but without the consent of the author must retain this paragraph, and in the article page obvious location to the original link, otherwise reserves the right to pursue legal responsibility.
The article was also published in my Independent blog-petter Liu blog.

ieee829-2008 Software Test Documentation Standard Introduction