FIT4004 Lecture Notes - Lecture 6: Test Case, Test Plan, Unique Identifier
15 Jun 2018
School
Department
Course
Professor
Week 6 - Document testing
Testing documentation required to communicate with testers on what needs to be done
and also as a record of what testing has been done (especially useful if testing is
outsourced in organisations)
Project test plans
Consist of:
●Testing strategy - should be based on the risks to be addressed and the
resources available
●Testing artifacts: what artifacts need to be produced to conduct this testing,
including code and other documents
●Test environment - What tools, specialized testing software, and hardware
resources will be required to conduct testing?
●Personnel -Who will be responsible for conducting all aspects of the testing
process?
●Scheduling: When will testing be conducted?
●Results reporting: How will the results of testing, particularly unexpected results,
be made available to the relevant people - and how are the "relevant" people for
a failed test known?
●Metrics: What metrics will you collect from your testing?
Test cases and procedures
Vital documents for test cases and procedures
●Test environment - hardware & software required to run tests
●Test procedure - common setup procedure, set of test cases & order to execute
●Test case - inputs and expected results
Test Cases must contain:
●Unique identifier
●Scope of test(s)
●Objective - can be descriptive title or a separate section
Document Summary
Testing documentation required to communicate with testers on what needs to be done and also as a record of what testing has been done (especially useful if testing is outsourced in organisations) Testing strategy - should be based on the risks to be addressed and the resources available. Testing artifacts: what artifacts need to be produced to conduct this testing, including code and other documents. Test environment - hardware & software required to run tests. Test procedure - common setup procedure, set of test cases & order to execute. Test case - inputs and expected results. Objective - can be descriptive title or a separate section. Link to relevant requirement that is being tested (can be done in a separate document called traceability matrix) Detailed, unambiguous descriptions on how to perform test case. Any deviations from the procedure (note: this shouldn"t happen, but if it does, there needs to be some record of why).
