Computer Applications Practicum

Required Test Documentation

Spring 2011

The purpose of the test documentation is to demonstrate that the software meets the system requirements specification, or show any specific cases in which the software does not perform as originally expected. The procedures used to test your program should be recorded and submitted in the following format.

Test documentation for each functional requirement:

  1. Description of test cases:
    1. Inputs - These may be either data files, sequences of GUI actions, or a set of values submitted on a form
    2. Expected outputs For requirements that include end user input, test cases should be included both for normal values, and also for boundary conditions to check whether inappropriate user input is handled gracefully.
  2. For each test case record:
    1. when test run was performed
    2. any results that differ from expected outputs
    3. log of actions taken to correct any faults
  3. List of unresolved issues (known bugs or unimplemented features)
The test cases should be ordered according to the prioritised list of functional requirements from your requirements specification document. This will make it possible to quickly determine the implementation status of each requirement.

-- JimSkon - 2011-04-26

Topic attachments
I Attachment Action Size Date Who Comment
Docdoc test_doc_dmeyer1.doc manage 16.5 K 2011-05-15 - 20:09 DerrickMeyer  
Topic revision: r2 - 2011-05-15 - DerrickMeyer
 
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback