November 21st, 2008 chris
The Test Summary Report summarizes the results of the testing activities and provides an evaluation based on these results.
It is composed of the following 8 sections:
- Test summary report identifier
- Summary
- Variance
- Comprehensive assessment
- Summary of results
- Evaluation
- Summary of activities
- Approvals
Posted in Software Testing
November 21st, 2008 chris
The Test Incident Report documents any event observed during testing that requires further investigation.
It is composed of the following 4 sections:
- Test incident report identifier
- Summary
- Incident description
- Impact
Posted in Software Testing
November 21st, 2008 chris
The Test Log provides a chronological record about relevant details observed during the test execution.
It is composed of the following 3 sections:
- Test log identifier
- Description
- Activity and event entries
Posted in Software Testing
November 21st, 2008 chris
The Test Item Transmittal Report specifies the test items being provided for testing.
It is composed of the following 5 sections:
- Transmittal report identifier
- Transmitted items
- Location
- Status
- Approvals
Posted in Software Testing
November 21st, 2008 chris
The Test Procedure Specification specifies the steps for executing a test case and the process for determining whether the software passed or failed the test.
It is composed of the following 4 sections:
- Test procedure specification identifier
- Purpose
- Special requirements
- Procedure steps
Posted in Software Testing
November 21st, 2008 chris
The test case specification specifies in detail each test case listed in the test design specification.
It is composed of the following 7 sections:
- Test case specification identifier
- Test items
- Input specifications
- Output specifications
- Environmental needs
- Special procedural requirements
- Intercase dependencies
Posted in Software Testing
November 21st, 2008 chris
The Test Design Specification identifies a set of features to be tested and describes a group of test cases that will adequately test those features.
It is composed of the following 5 sections:
- Test design specification identifier
- Features to be tested
- Approach refinements
- Test identification
- Feature pass/fail criteria
Posted in Software Testing
July 23rd, 2008 chris
The Test Plan Document describes the scope, approach, resources, and schedule of the testing activities.
It is composed of the following 16 Sections:
- Test plan identifier
- Introduction
- Test items
- Features to be tested
- Features not to be tested
- Approach
- Item pass/fail criteria
- Suspension criteria and resumption requirements
- Test deliverables
- Testing tasks
- Environmental needs
- Responsibilities
- Staffing and training needs
- Schedule
- Risks and contingencies
- Approvals
Posted in Software Testing
July 23rd, 2008 chris
Eight documents that can be used in software testing according to IEEE Standard for Software Test Documentation
- Test plan
- Test design specification
- Test case specification
- Test procedure specification
- Test item transmittal report
- Test log
- Test incident report
- Test summary report
Posted in Software Testing
July 10th, 2008 chris
White box testing is a strategy in which testing is based on the internal paths, structure, and implementation of the software under test (SUT). Unlike its complement, black box testing, white box testing generally requires detailed programming skills.
The general white box testing process is:
- The SUT’s implementation is analyzed.
- Paths through the SUT are identified.
- Inputs are chosen to cause the SUT to execute selected paths. This is called path sensitization. Expected results for those inputs are determined.
- The tests are run.
- Actual outputs are compared with the expected outputs.
- A determination is made as to the proper functioning of the SUT.
Posted in Software Testing