Friday, 16 January 2009

Unit test recording

I am in the process of working with some developers in ensuring that they produce an acceptable level of unit test evidence. This can cause issues as we dont wish to add a large overhead to the unit testing process by mandating the use of test scripts and formal test execution but at the same time require some record that the unit testing has been performed.

What is being trialled so far with some development acceptance is a simple document asking for information on the :
Introductory Information
  • System - Software application that is being worked on.
  • Project - Project Name and Code
  • Change - What is being tested? could be the whole system or could be a small new feature.
Tabulated
  • Tester - Person performing the unit testing (Ideally not the developer of the code.)
  • Test ID - Identification for individual test
  • Input - Quick summary of what action is required (e.g. click all close buttons)
  • Expected Output - Quick summary of what is expected (e.g. application should close successfully with no exceptions or memory leaks)
  • Test passed - Y/N
  • Issues - Any issues outstanding.

This it is hoped will help prevent certain areas of unit testing being missed and greatly increase the overall quality of the end solutions.

No comments: