Talk:Software test documentation

This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Software: Computing Mid‑importance This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.SoftwareWikipedia:WikiProject SoftwareTemplate:WikiProject Softwaresoftware articles Mid This article has been rated as Mid-importance on the project's importance scale. This article is supported by WikiProject Computing.

The following sentence is subject to 2 or 3 different interpretations. Could the original author or other qualified person reword the sentence to eliminate ambiguity? "The report will also include, if possible, an assessment of the impact upon testing of an incident." --> Fixed, 1 June 2009 [donmillion]

This article is out of date; IEEE 829-1998 was superceded IEEE 829 in November of 2008. Unlike previous revisions, this is a complete rewrite of the standard, which depicts test documentation as an output of testing tasks, rather than a self-contained entity. The standard (IEEE 829-2008) no longer prescribes specific tables of contents for test documentation, but uses a scheme of "integrity levels" to define what test tasks, and hence what levels and contents of test documentation, might be appropriate to different levels of project and product risk.

It will be some time before the revised standard achieves widespread use, so possibly two articles are needed, a new one designated "IEEE 829-2008", and the current one re-designated "IEEE 829-1998".

Donmillion (talk) 08:18, 1 June 2009 (UTC)[reply]

IEEE 829-2008 has, itself, been superseded by ISO/IEC/IEEE 29119-3:2013^[1].

I've tweaked the article as is, but suggest it needs wholesale revision...

Andrew D Banks (talk) 11:18, 13 October 2017 (UTC)[reply]

This article only discusses test documentation standards, which are completely ignored by a large swath of the software industry. Is the scope of this article supposed to include broad coverage of how software test documentation is done in practice? Faught (talk) 20:21, 26 December 2017 (UTC)[reply]

I think the name of this article is wrong, as the concept of "software test documentation" as a hyponym of any standard, like IEEE 829. This article should be renamed by deleting the redirection IEEE_829 and moving the article "Software test documentation" to "IEEE 829".--Sae1962 (talk) 08:46, 18 January 2018 (UTC)[reply]

Agreed, but how about "IEEE 829-2008"? Faught (talk) 23:50, 22 January 2018 (UTC)[reply]

There is a move discussion in progress on Template talk:IEEE software documents which affects this page. Please participate on that page and not in this talk page section. Thank you. —RMCD bot 22:02, 15 June 2020 (UTC)[reply]

Is this article intended to be about the overall issue of software test documentation or is it specific to IEEE 829 requirements? — GhostInTheMachine ^{talk to me} 21:42, 5 December 2021 (UTC)[reply]