2b
Test to ensure that the sheet tabs were removed from the screen upon running of the macro. One shot is needed as when removed sheet tabs are removed from all of the sheets.
2c
Test as to whether all of the editing toolbars are removed once the macro is run. Again only one print is needed as the toolbars are removed from the user interface not each individual sheet.
2d
An integrated macro which runs all of 2a, 2b and 2c in one go. Requires a selection of screenshots to show that the macros run correctly on each sheet.
2e
Performs the opposite action to 2a in replacing the row and column headings, this requires more than one screen shot due to the fact that the row and column headings are replaced on each sheet individually.
2f
Replaces the sheet tabs removed by 2b, requires only one screen shot due to the tabs being removed from the interface not from each sheet.
2g
Replaces a selection of editing toolbars which are most commonly used, will not need multiple shots due to the toolbars being on the interface not the sheets.
2h
Replaces all of the row and column headings as well as the sheet tabs and some toolbars. It is an integrated macro which runs 2e, 2f and 2g. A selection of screen shots will be required as the row and column headings are replaced on all the sheets separately.
2i
This macro is found on every sheet except for the main menu, this is because it takes the user from anywhere to the main menu screen, a before and after shot will be needed
Before After
Testing for LookupMenu
3a
Takes the user to table Starter on the sheet “LookupMenu”. A before and after shot will be taken.
The test proved the macro to work correctly.
3b to 3f
All of 3b to 3f perform the same function as 3a, screen shots will not be taken but the results of the tests will be input on the table below.
Testing for LookupTables
The only tests for this sheet is the naming of the tables, these will be tested by typing the name of the table into the Name Box, if the test is successful then the area named will be selected. Below is a table of results for the tests.
Testing Plan for DataEntry
4a
This macro should clear the contents of the data entry sheet ready for the next data to be entered. Two screen shots will be produced.
The first screen shot has all the data entered that would be entered by a customer and the second shot is of the screen after the macro was run, areas where data was entered are clear and all the combo boxes are reset to none selected. The test proved the macro to run correctly.
4b
This test is to see whether the macro FinishEntry works as specified. A shot will be shown of the data on the data entry screen and again on the event records screen. Any test that found faults in the macro would be shown also.
4c
This module tests all of the formulae on the sheet DataEntry, screen shots will be produce of the before screen as well as two sets of data from the four to be used. Any tests which are failed will be noted and a reason or explanation suggested.
Before Extreme Data (Low)
Incorrect Data
The cells B24 and F24 are not protected against text being input so the formulae that use these cells do not work, this is not a problem with the formula but a problem with the validation of the sheet.
4d
Tests on the lookup functions within the sheet such as those involved in the Combo Boxes and the formulae associated with them i.e. the INDEX formulae. Two screen shots will be shown, both of the sheet at different stages of testing, a shot showing the sheet before the testing will not be needed as this exists already in other modules. Any faults found will be noted.
Testing for EventRecords
5a
This test is to see whether the macro PrintLine works as specified. This test could not be performed as the macro has not been written yet. On completion of the macro it will be tested as planned.
