Testing

Discussion

Investigation

Design

Prototype

Post Prototype

Developmental Testing

Software Development

Evaluation

Testing - 10 marks

What does it need to contain?

Take note of the highlighted KEY words

Note: The main purpose of the Testing section is to show your final solution working. There is no need to show tests which cause your system to crash, or show errors in your code - you will have done this in Developmental Testing.

Test Plan

Purpose - Produce a comprehensive plan for testing all areas of the system i.e. write a list of tests that you will run on your system to prove that it works.

What do I need to do?:

Copy your list of objectives from your Investigation document
For each objective, write a Test Plan. Make sure your test data and expected results are in sufficient detail that a third party could run your tests on your system. You should have a separate test plan for each objective. Some test plans will have many tests, some only one or two tests.
Include functional, unit, system and integration testing. No need to test lots of navigation buttons.
Inlcude some validation testing. Note: you do not have to test ALL validation implemented, just one or two examples of each type of validation check, using both valid (normal, extreme) AND invalid (erroneous) data.
Make use of test data including typical, extreme and invalid (erroneous) data where appropriate. Your test data must be detailed e.g. if you plan to test adding a record, your test data must provide all the pieces of data you want to insert into your textfile.

Test Plan:

Test No: A sequential number, which can be used to refer to a test, when you are snipping your envidence
Description: Explain exactly what you are trying to check i.e. what is the purpose of this test
Test Data: Anyactual inputs the tester has to enter to make the test run (e.g. username and password to log on)
Expected Results: Describe what you expect to happen - should be written BEFORE you run the test
Actual Results: Describe what happened. Usually this will be a screenshot as evidence. Don't put the screenshot in this column, just say 'See evidence below' or look at example below

Test Plan Examples:

Note: In Test 1, the test data column has the actual data to be entered, to make the test run as expected.

In tests 3 to 7 below, we are testing data validation. A range check has been coded to ensure the number of Personal Fouls is sensible, i.e. between 0 and 5.

Note: Any validation check will require at least two tests, firstly using data which will be accepted by the system, then another test which shows an error message being produced e.g. login test - Test 1: Enter valid username, Test 2: Enter invalid username.

A single range check requires a number of tests:

Test 3: Test extreme data. Still valid - the lower boundary (value of 0)

Test 4: Test extreme data. Still valid - the upper boundary (value of 5)

Test 5: Test erroneous (invalid) data (value of -1)

Test 6: Test erroneous (invalid) data (value of 6)

Test 7: Test normal (acceptable) data, in the middle of the range

Some tests need data input to run the system, not as input for validation. In this example the user has to enter a MatchId, to display all details of that match.

Some tests do not need data input, so the Test Data column can be left blank.

Although test data is not required for this test, it would be useful to add which button has to be pressed, to make the system display the fixtures as requested.

2. Test Evidence

Purpose - Produce annotated test runs that include commentaries on the outcomes of the testing process.

What do I need to do?:

Underneath each test plan, put a heading for each of the tests e.g. Test 1, Test 2, Test 3.
For each of your tests in your test plans, screenshot the result of running the test in your system under the appropriate heading.
Annotate all test evidence screenshots to explain what the evidence is proving (state the obvious!)
Include specific suggestions to refine the system as a result of your test outcome, where appropriate.