Overview of Test Plan

This framework consists of 3 main components that are used to form test plans for both server infrastructure and business systems at Braintree District Council.

• Systems - This is the main entity (either a server, or business system) which groups Test Cases and Test Runs.
• Test Cases - These define an area to test and include steps of how to complete the test, along with an expected outcome.
• Test Runs - These capture the output of system testing conducted at a given time. These include a copy of the Test Cases, the results/outcomes from completing them, and an overall status (Pass/Fail) for the testing completed.

Systems

A system is a main entity that is used to define the scope for the test plan. For example, a server such as BDCFILE01 or a business system such as the IDOX DMS.

These systems can be broken down further (e.g. to allow test plans for each department within a corporate system such as Uniform).

Systems have 2 levels of permissions - Editor and Viewer.

Editors can update permissions and edit the test cases for a system.

Viewers can only view test cases and submit test runs.

Test Cases

Test cases (or test scenarios) are the individual areas that you want to test within a system. For example, logging into a system would be a test case.

Under each test case, we have steps and an expected outcome:

Steps

These are the individual actions needed in order to perform the test scenario. Each test case needs at least 1 step.

Expected Outcome

The expected outcome is the result that should be produced at the end of following the steps in the test case.

This is used as a baseline to determine if a test has passed or failed.

Test Runs

Test runs form the recording/documentation of completing testing using test cases for a system. These allow you to check off each step as they are completed, mark if a test case has passed or failed, and make optional notes.

Test runs can either contain some or all of the test cases for a system (depending on the requirements for testing). A copy of test cases is saved into the test run (meaning that future changes to test cases won't impact previous test runs). Optionally, the results of a test run can be emailed to anyone in the Council (if required).

When a test run is marked as completed, it becomes read-only and cannot be edited. PDF versions of test runs (both reports and forms) can be printed from Test Plan if needed.

Editors - people who can edit test cases and update permissions.

Viewers - people who can only view test cases and submit test runs.