Software test documentation: Difference between revisions

Revision as of 21:42, 26 June 2022

Latest revision as of 11:26, 16 August 2025

(5 intermediate revisions by 5 users not shown)

Line 1:

{{Short description|IEEE standard}}

{{useUse dmy dates|date=MarchDecember 20122023}}

{{IEEE software documents}}

'''Software test documentation''' is the vital element that raises any experimental activities to the level of a [[software test]].<ref>{{cite web | url = http://www.the-software-experts.com/e_dta-sw-test-doku.php | title = Software Test Documentation – How should Test Documentation look like? | publisher = THE-SOFTWARE-EXPERTS | access-date = 2017-01-18 }}</ref> International organisations like IEEE and ISO have published standards for software test documentation.

==Status of IEEE 829==

Note: '''IEEE 829-2008''' has been superseded by [[ISO/IEC 29119|ISO/IEC/IEEE 29119-3:2013]].<ref name="IEEEstatus">{{cite web|title=IEEE Products and Projects Status Report|url=http://standards.ieee.org/develop/project/status.txt|websitearchive-url=https://web.archive.org/web/20120212232505/http://standards.ieee.org/develop/project/status.txt|url-status=dead|archive-date=12 February 2012|website=[[IEEE]]|access-date=13 October 2017}}</ref>

==Background to IEEE 829==

Line 15 ⟶ 13:

*'''Master Test Plan''' (MTP): The purpose of the Master [[Test Plan]] (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across multiple projects).

*'''Level Test Plan''' (LTP): For each LTP the scope, approach, resources, and schedule of the testing activities for its specified level of testing need to be described. The items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the associated risk(s) need to be identified.

*'''Level [[Test Design]]''' (LTD): Detailing [[Test case (software)|test case]]s and the expected results as well as test pass criteria.

*'''Level Test Case''' (LTC): Specifying the test data for use in running the test cases identified in the Level Test Design.

*'''Level Test Procedure''' (LTPr): Detailing how to run each test, including any set-up preconditions and the steps that need to be followed.

Line 27 ⟶ 25:

The standard formed part of the training syllabus of the [[ISEB]] Foundation and Practitioner Certificates in Software Testing promoted by the [[British Computer Society]]. [[ISTQB]], following the formation of its own syllabus based on [[ISEB]]'s and Germany's [[ASQF]] syllabi, also adopted IEEE 829 as the reference standard for software and system test documentation.

Dr. [[Dave Gelperin|David Gelperin]] and Dr. [[William C. Hetzel]] developed the Systematic Test and Evaluation Process (STEP) methodology in order to implement the original IEEE-829 Standard for Software Test Documentation.<ref name="CraigJaskiel2002">{{cite book|author1=Rick D. Craig|author2=Stefan P. Jaskiel|title=Systematic Software Testing|url=https://books.google.com/books?id=2_gbZYZcZXgC|date=2002|publisher=Artech House|isbn=978-1-58053-792-6|page=4}}</ref>

==References==

Line 37 ⟶ 35:

{{IEEE standards}}

[[Category:Software testing|documentation]]

[[Category:Software documentation]]

[[Category:IEEE standards]]