Test Plans & Data

Test Plan

A test plan is a document that outlines the approach, objectives, scope, and resources required for testing a software system. It serves as a roadmap for the testing process and ensures that all aspects of the software are thoroughly tested.

A typical test plan includes the following sections, amongst others::

1. Test Scope: Defines the boundaries and limitations of the testing, including the features and functionalities to be tested.
2. Test Strategy: Outlines the overall approach to be followed during testing, such as the testing techniques, tools, and environments.
3. Test Environment: Describes the hardware, software, and network configurations required for testing.
4. Test Deliverables: Lists the expected outputs and documents to be produced during testing, such as test cases, test reports, and defect logs.

 

Test Data

When creating a test plan and testing table, it is important to consider the different categories of data that are to be tested, including  a variety of valid and invalid types. Including:

Boundary Values

Test data should include values at the boundaries of input ranges, both within and outside the expected limits.

Valid Inputs

Test data should cover all valid inputs for each test case, ensuring the software functions correctly for expected scenarios.
Invalid Inputs

Test data should include invalid inputs to test how the software handles errors, exceptions, and unexpected situations.

Edge Cases

Test data should cover edge cases, unusual scenarios, and exceptional conditions that might occur during normal system usage.
Combinations and Variations: Test data should encompass different combinations and variations of input values to test the software’s behavior under various conditions.

Performance Data

For performance testing, test data should include realistic data sets that reflect the expected usage patterns and load on the system.

Negative Testing

Test data should include negative scenarios to ensure that the software correctly detects and handles errors, security vulnerabilities, and invalid inputs.

Testing Table

In GCSE Computer Science, one common technique for organizing and documenting test cases is through the use of a testing table or a test plan table. This table helps to systematically document the test scenarios, inputs, expected outputs, and actual outputs during the testing process.

Test Case	Inputs	Expected Output	Actual Output	Pass/Fail
Correct Username & password	“bob” “Password123”	Pass
Empty username & passowrd	“” “”	Fail
Correct username no passowrd	“bob” “”	Fail
Empty username, correct password	“” “Password123”	Fail
Correct username, password no capitals	“bob” “password123”	Fail

Resources