IEEE829-1998IEEE829-2008,alsoknownasthe829StandardforSoftwareandSystemTestDocumentation,isanIEEEstandardthatspecifiestheformofasetofdocumentsforuseineightdefinedstagesofsoftwaretestingandsystemtesting,eachstagepotentiallyproducingitsownseparatetypeofdocument.Thestandardspecifiestheformatofthesedocuments,butdoesnotstipulatewhethertheymustallbeproduced,nordoesitincludeanycriteriaregardingadequatecontentforthesedocuments.Theseareamatterofjudgmentoutsidethepurviewofthestandard.Thedocumentsare:MasterTestPlan:ThepurposeoftheMasterTestPlanistoprovideanoveralltestplanningandtestmanagementdocumentformultiplelevelsoftest.LevelTestPlan:ForeachLTPthescope,approach,resources,andscheduleofthetestingactivitiesforitsspecifiedleveloftestingneedtobedescribed.Theitemsbeingtested,thefeaturestobetested,thetestingtaskstobeperformed,thepersonnelresponsibleforeachtask,andtheassociatedriskneedtobeidentified.LevelTestDesign:Detailingtestcasesandtheexpectedresultsaswellastestpasscriteria.

TestPlanAtestplanisadocumentdetailingasystematicapproachtotestingasystemsuchasamachineorsoftware.Theplantypicallycontainsadetailedunderstandingoftheeventualworkflow.

TestSummaryReportTestsummaryreportisthereportwhichispreparedaftertestingiscomplete.

TestCaseSpecificationTheClassificationTreeMethodisamethodfortestdesign,asitisusedindifferentareasofsoftwaredevelopment.IthasbeendevelopedbyGrimmandGrochtmannin1993.ClassificationTreesintermsoftheClassificationTreeMethodmustnotbeconfusedwithdecisiontrees.Theclassificationtreemethodconsistsoftwomajorsteps:IdentificationoftestrelevantaspectsandtheircorrespondingvaluesaswellasCombinationofdifferentclassesfromallclassificationsintotestcases.Theidentificationoftestrelevantaspectsusuallyfollowsthespecificationofthesystemundertest.Theseaspectsformtheinputandoutputdataspaceofthetestobject.Thesecondstepoftestdesignthenfollowstheprinciplesofcombinatorialtestdesign.Whilethemethodcanbeappliedusingapenandapaper,theusualwayinvolvestheusageoftheClassificationTreeEditor,asoftwaretoolimplementingtheclassificationtreemethod.

TestProcedure/Scriptspecification-TestProcedure-Manual-TestScript-Automated

TestDesignspecificationSpecificationmayrefertoanexplicitsetofrequirementstobesatisfiedbyamaterial,design,product,orservice.Shouldamaterial,product,orservicefailtomeetoneormoreoftheapplicablespecifications,itmaybereferredtoasbeingoutofspecification;theabbreviationOOSmayalsobeused.Incasualusage,underspecoroverspecareusedwhensomethingisworseorbetterthanspecified,thoughingeneralthereisonlyanotionof"inspec"or"outofspec",not"better"or"worse".Aspecificationisatypeoftechnicalstandard.Atechnicalspecificationmaybedevelopedbyanyofvariouskindsoforganizations,bothpublicandprivate.Exampleorganizationtypesincludeacorporation,aconsortium,atradeassociation,anationalgovernment,aprofessionalassociation,apurpose-madestandardsorganizationsuchasISO,orvendor-neutraldevelopedgenericrequirements.Itiscommonforoneorganizationtorefertothestandardsofanother.Voluntarystandardsmaybecomemandatoryifadoptedbyagovernmentorbusinesscontract.

TestIncidentReportTestIncidentReportisanothernameforbugreport.

Ishowincidentsarereportedwithasmuchinformationaspossibletohelpdeveloperssolvetheissue.Involvesincidentdescriptionandtheimpactoftheissue.