Software test documentation - Revision history

GreenC bot: Rescued 1 archive link; Move 2 urls. Wayback Medic 2.5 per WP:URLREQ#ieee.org

2024-07-31T05:02:23Z

Rescued 1 archive link; Move 2 urls. Wayback Medic 2.5 per WP:URLREQ#ieee.org

← Previous revision		Revision as of 05:02, 31 July 2024
Line 4:		Line 4:

	==Status of IEEE 829==		==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\|~~website~~=standards.ieee.org\|access-date=13 October 2017}}</ref>		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\|archive-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==		==Background to IEEE 829==

Tom.Reding: /* top */Confirm {{Use dmy dates}} from 2012; WP:GenFixes & cleanup on

2023-12-13T21:10:05Z

top: Confirm {{Use dmy dates}} from 2012; WP:GenFixes & cleanup on

← Previous revision		Revision as of 21:10, 13 December 2023
Line 1:		Line 1:
	{{Short description\|IEEE standard}}		{{Short description\|IEEE standard}}
	{{~~use~~ dmy dates\|date=~~March~~ ~~2012~~}}		{{Use dmy dates\|date=December 2023}}
	{{IEEE software documents}}		{{IEEE software documents}}

HeyElliott: /* External links */ WP:SORTKEY

2023-11-22T23:10:22Z

External links: WP:SORTKEY

← Previous revision		Revision as of 23:10, 22 November 2023
Line 35:		Line 35:
	{{IEEE standards}}		{{IEEE standards}}

	[[Category:Software testing]]		[[Category:Software testing\|documentation]]
	[[Category:Software documentation]]		[[Category:Software documentation]]
	[[Category:IEEE standards]]		[[Category:IEEE standards]]

Partofthemachine: /* Use of IEEE 829 */

2023-02-04T23:19:09Z

Use of IEEE 829

← Previous revision		Revision as of 23:19, 4 February 2023
Line 25:		Line 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.		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>		Dr. [[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==		==References==

Attila Zsolt Somogyi: Remove broken link

2022-08-21T19:11:21Z

Remove broken link

← Previous revision		Revision as of 19:11, 21 August 2022
Line 2:		Line 2:
	{{use dmy dates\|date=March 2012}}		{{use dmy dates\|date=March 2012}}
	{{IEEE software documents}}		{{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==		==Status of IEEE 829==

Jimmy Olano: Importing Wikidata short description: "IEEE standard"

2022-06-26T21:42:14Z

Importing Wikidata short description: "IEEE standard"

← Previous revision		Revision as of 21:42, 26 June 2022
Line 1:		Line 1:
			{{Short description\|IEEE standard}}
	{{use dmy dates\|date=March 2012}}		{{use dmy dates\|date=March 2012}}
	{{IEEE software documents}}		{{IEEE software documents}}

Monkbot: Task 18 (cosmetic): eval 3 templates: hyphenate params (1×);

2021-01-23T19:51:17Z

Task 18 (cosmetic): eval 3 templates: hyphenate params (1×);

← Previous revision		Revision as of 19:51, 23 January 2021
Line 5:		Line 5:

	==Status of IEEE 829==		==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\|website=standards.ieee.org\|~~accessdate~~=13 October 2017}}</ref>		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\|website=standards.ieee.org\|access-date=13 October 2017}}</ref>

	==Background to IEEE 829==		==Background to IEEE 829==

RMCD bot: Removing notice of move discussion

2020-06-22T07:04:31Z

Removing notice of move discussion

← Previous revision		Revision as of 07:04, 22 June 2020
Line 1:		Line 1:
		⚫	{{use dmy dates\|date=March 2012}}
	<noinclude>{{User:RMCD bot/subject notice\|1=IEEE 829\|2=Template talk:IEEE software documents#Requested move 15 June 2020 }}
⚫	~~</noinclude>~~{{use dmy dates\|date=March 2012}}
	{{IEEE software documents}}		{{IEEE software documents}}

RMCD bot: Notifying subject page of move discussion on Template talk:IEEE software documents

2020-06-15T22:02:40Z

Notifying subject page of move discussion on Template talk:IEEE software documents

← Previous revision		Revision as of 22:02, 15 June 2020
Line 1:		Line 1:
			<noinclude>{{User:RMCD bot/subject notice\|1=IEEE 829\|2=Template talk:IEEE software documents#Requested move 15 June 2020 }}
	{{use dmy dates\|date=March 2012}}		</noinclude>{{use dmy dates\|date=March 2012}}
	{{IEEE software documents}}		{{IEEE software documents}}

51.219.158.83: changed the spelling of summarise (z to s)

2020-01-30T16:06:59Z

changed the spelling of summarise (z to s)

← Previous revision		Revision as of 16:06, 30 January 2020
Line 19:		Line 19:
	*'''Level Test Log''' (LTL): To provide a chronological record of relevant details about the execution of tests, e.g. recording which tests cases were run, who ran them, in what order, and whether each test passed or failed.		*'''Level Test Log''' (LTL): To provide a chronological record of relevant details about the execution of tests, e.g. recording which tests cases were run, who ran them, in what order, and whether each test passed or failed.
	*'''Anomaly Report''' (AR): To document any event that occurs during the testing process that requires investigation. This may be called a problem, test incident, defect, trouble, issue, anomaly, or error report. This document is deliberately named as an anomaly report, and not a fault report. The reason is that a discrepancy between expected and actual results can occur for a number of reasons other than a fault in the system. These include the expected results being wrong, the test being run incorrectly, or inconsistency in the requirements meaning that more than one interpretation could be made. The report consists of all details of the incident such as actual and expected results, when it failed, and any supporting evidence that will help in its resolution. The report will also include, if possible, an assessment of the impact of an incident upon testing.		*'''Anomaly Report''' (AR): To document any event that occurs during the testing process that requires investigation. This may be called a problem, test incident, defect, trouble, issue, anomaly, or error report. This document is deliberately named as an anomaly report, and not a fault report. The reason is that a discrepancy between expected and actual results can occur for a number of reasons other than a fault in the system. These include the expected results being wrong, the test being run incorrectly, or inconsistency in the requirements meaning that more than one interpretation could be made. The report consists of all details of the incident such as actual and expected results, when it failed, and any supporting evidence that will help in its resolution. The report will also include, if possible, an assessment of the impact of an incident upon testing.
	*'''Level Interim Test Status Report''' (LITSR): To ~~summarize~~ the interim results of the designated testing activities and optionally to provide evaluations and recommendations based on the results for the specific test level.		*'''Level Interim Test Status Report''' (LITSR): To summarise the interim results of the designated testing activities and optionally to provide evaluations and recommendations based on the results for the specific test level.
	*'''Level Test Report''' (LTR): To ~~summarize~~ the results of the designated testing activities and to provide evaluations and recommendations based on the results after test execution has finished for the specific test level.		*'''Level Test Report''' (LTR): To summarise the results of the designated testing activities and to provide evaluations and recommendations based on the results after test execution has finished for the specific test level.
	*'''Master Test Report''' (MTR): To ~~summarize~~ the results of the levels of the designated testing activities and to provide evaluations based on these results. This report may be used by any ~~organization~~ using the MTP. A management report providing any important information uncovered by the tests accomplished, and including assessments of the quality of the testing effort, the quality of the software system under test, and statistics derived from Anomaly Reports. The report also records what testing was done and how long it took, in order to improve any future test planning. This final document is used to indicate whether the software system under test is fit for purpose according to whether or not it has met acceptance criteria defined by project stakeholders.		*'''Master Test Report''' (MTR): To summarise the results of the levels of the designated testing activities and to provide evaluations based on these results. This report may be used by any organisation using the MTP. A management report providing any important information uncovered by the tests accomplished, and including assessments of the quality of the testing effort, the quality of the software system under test, and statistics derived from Anomaly Reports. The report also records what testing was done and how long it took, in order to improve any future test planning. This final document is used to indicate whether the software system under test is fit for purpose according to whether or not it has met acceptance criteria defined by project stakeholders.

	==Use of IEEE 829==		==Use of IEEE 829==