Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / sm
IEEE 829-1998, also known as the 829 Standard for Software
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. The standard specifies the
format of these documents but does not stipulate whether
they all must be produced, nor does it include any criteria
regarding adequate content for these documents.
Test Plan: a management planning document that shows:
How the testing will be done (including SUT
configurations).
Who will do it
What will be tested
How long it will take (although this may vary, depending
upon resource availability).
What the test coverage will be, i.e. what quality level is
required
Test Design Specification: detailing test conditions and
the expected results as well as test pass criteria.
Test Case Specification: specifying the test data for use
in running the test conditions identified in the Test
Design Specification
Test Procedure Specification: detailing how to run each
test, including any set-up preconditions and the steps that
need to be followed
Test Item Transmittal Report: reporting on when tested
software components have progressed from one stage of
testing to the next
Test Log: recording which tests cases were run, who ran
them, in what order, and whether each test passed or failed
Test Incident Report: detailing, for any test that failed,
the actual versus expected result, and other information
intended to throw light on why a test has failed. This
document is deliberately named as an incident 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
wrongly, 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.
Test Summary Report: 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 Incident 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.
| Is This Answer Correct ? | 3 Yes | 0 No |
Post New Answer View All Answers
Should testing be done only after the build and execution phases are complete?
write the test case for Bulb & Mobile phone
How can a LOG for testcases be maitained which can give information about a TestCase that is it new one or has been occured in previous versions of the software.
What do you like about computers?
What are the different cost elements involved in implementing a process in an organization?
please send me database stored procedure checklist.
why use caffine for HPLC calibration ?
What is the test harness?
What is Dynamic Binding and Dynamic Loss?
What is black box testing, and what are the various techniques?
What is ecp (equivalence class partition)?
what s test block ratio? please any one answer me..
Which is the best testing model?
how to write manual testcases for download the files from the template. for example:from product cost enddate
Hello Varun, Kindly send me the material as well as sample question papers as i am interested in doing the certification. Kindly help me out in this regard. Here is my mail ID: bjyothitesting@gmail.com
