Home TEST DOCUMENTATION

TEST DOCUMENTATION

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 Plan
A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements.

Test Design Specification
The test design is the first stage in developing the tests for software testing projects. It records what needs to be tested, and is derived from the documents that come into the testing stage, such as requirements and designs.

Test Case Specification
Determines details of the specific data that is necessary to run tests based on the conditions identified in the test design specification

Test Procedure Specification
Specifies the steps for executing a set of test cases. How the test will run, the physical set-up required, and the procedure steps that need to be followed.

Test Item Transmittal Report
A detail of when specific tested items have been passed from one stage of testing to another.

Test Log
Logs what tests cases were run, who ran the tests, in what order they were run, and whether or not individual tests were passed or failed.

Test Incident Report
When one or more of the steps associated with a test case fail,  a Test Incident Report form lists the actual versus expected results of a test, and why the test failed.

Test Summary Report
A detail of all the important information to come out of the testing procedure, including an assessment of how well the testing was performed, an assessment of the quality of the system, any incidents that occurred, and a record of what testing was done and how long it took to be used in future test planning. This final document is used to determine if the software being tested is viable enough to proceed to the next stage of development.

 

 

default image

“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 March 25, 2016

<< Prev
Next >>
© 2012 - 2017 BAD TESTING®, LLC.

Bad Testing, LLC ® is a software QA company that offers computer and technological professional services, namely software quality assurance. BadTesting.com, a software QA website, introduces testing concepts and techniques associated with internet applications.