Test processes determine whether the development products of a given activity conform to the requirements of that activity and whether the system and/or software satisfies its intended use and user needs. The scope of testing encompasses software-based systems, computer software, hardware, and their interfaces.

829-2008 – IEEE Standard for Software and System Test Documentation, is an IEEE standard that specifies the form of a set of documents for use in eight defined stages of software testing, each stage potentially producing its own separate type of document.

Software quality assurance test documentation includes:

Test Case Specification

The Test Case Specification is developed in the Development Phase by the organization responsible for the formal testing of the application. A Test Case Specification describes the purpose of a specific test, identifies the required inputs and expected results, provides step-by-step procedures for executing the test, and outlines the pass/fail criteria for determining acceptance.

Test Cases

Test cases are a set of conditions or variables under which a tester will determine if a requirement upon an application is partially or fully satisfied.

  • There must be at least one test case for each requirement for traceability.
  • Each test case will have a known input and an expected output, worked out before the test.

Test Scripts

Test Scripts are a set of instructions that will be performed on the System to test that the system functions as expected. These steps can be executed manually or automatically.

  • Can either be written using a special automated functional GUI test tool or in a well known programming language.
  • Automated test tools can test many areas of system functionality such as the user interface, performance of the system, the system code and the requirements.
  • Automated testing has the advantage over manual testing in that it is easily repeatable, and thus is favored when doing regression testing.

IEEE 829 Test Case Specification Template

Test Case Specification Identifier
Test Items
Describe features and conditions tested

Input Specifications
Data Names
Values (with tolerances or generation procedures)

Output Specifications
Data Names
Values (with tolerances or generation procedures)

Environmental Needs

Special Procedural Requirements
Inter-Case Dependencies

“BAD Testing has been our trusted partner for our most vital clients. We know we can count on a thorough, knowledgeable test team no matter the timeline or the technology. They know how to integrate seamlessly with a team of any size and don’t require any hand-holding and hit the ground running. They are stunningly up-to-date on trends and always able to support the team with the right solution to tough technical problems. Whether it’s a tight timeline or challenging technical work, my first and last call is to BAD Testing.”

Dan Lavorini Vice President, Technical Director - Edelman Digital

<< Prev
Next >>