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
I have 2 yrs 10 months experience in manual testing. there is a gap of 3 yrs in between. just 3 months before i rejoined the same company. I am looking for new & better job.What I have to enhance my career to up level, should I have to do Automation course or any other. Guide me properly.
Can anyone please tell in detail about the Rally tool and how a tester is going to use it.
Test cases have written according to Flow of the software working or according to Screens?
can anyone tell anyone is providing training for CSTE exam in bangalore? and can u send some links related to this?
What is the difference between a standalone application, client-server application and web application?
Hi I am searching job please send some details abuot ERP project and real time test plan,traceability report,test case if any relate to erp project Please help me out to get a job in testing.my email address is chiku_69@yahoo.in Thank u
Hi, I was asked following question during a interview. Please answer it: Password field is there,we can accepts every character except underscore and semicolon. It can accept min 6 characters and maximum 12 characters. Prepare boundary value and equivalence class test cases.
Hi friends I am kranti completed my IT diploma in 2005 & after that complete my software testing course. Now I am working in small software form as software tester. I have 2 + year experience in manual testing. Now I wan to change company. Plz told me is there any effect that I can not have any degree although I have 2 + experience ?
How do you know the code has met specifications?
There are some features to improve the performance of a Product. What are those factors?
Beyond the customary advantages of having a testing group, what are the benefits does a company receive from a well run, automated testing group?
How do you get programmers to build testability support into their code?
Explain about PET Model?
how to create automation frame work ?
How to test a Falsh player scrollings?
