test case suite
|
What Why? The degree to which the test case suite is built into the test process, depends on the attitude to testing. Some organisations will have a formalized approach with lots of documentation. Others may use the opposite have an implicit acceptance. Typically this is posed verbally in the question "have you tested everything?" Who? Alternatively a formal structure may exist. For example a senior test analyst, might lay down guidelines on which features are to be tested. Junior analysts will actually select the cases. The test suite will then be executed either manually or with automated tools by test engineers or technician. Where?
When?
How? In a very formal setup with a high level of ceremony, producing a suite of tests is a much more onerous affair. A Test Design Specification may be drawn up following guidelines in IEEE829:1998. This will show which features are to be tested and how. The nature of the document is coarse grained. With greater granularity a test case specification is required for each test case. The test case suite and accompanying documentation may undergo a full inspection. Traceability will have to be shown from from each requirement. If a requirement is not fully tested then, this will have to be explained. In reality most test case suites are produced between these two extremes. For example a document might be produced called the test spec. The spec does not conform to any recognised standard, but it does provide a record of the testing taking place and the tests undertaken.
|
Related Articles
Similar Areas Selected Books
Keywords
|