Testing Strategy
This is actually part of design... BUT as it is very important we have decided to separate it.. It is VERY unlikely that you wont' add tests to your testing strategy as you develop the system... But we want to see a representative set of test that show us you know what you are doing.
You will see from the exemplars there are several ways to organise testing... BUT the following is one simple way that will work for most projects.
TestData
Whist not essential, It is a real time saver to say what your test data set is going to be. It needs to be big enough for the tests to be
Unit testing (White Box)
Done during development: you have a tricky method or a behavior of a class... Use Trace Tables or Handwritten calculations to show what the expected values are and then you step though the code to show this is the case. Just listing the Unit test you think you are likely to need at this stage will be fine. When you perform the test you can use screenshots or screencast vids for evidence.
GUI, IO testing (TEX: Typical, Erroneous, eXtreme)
All inputs need to be validated and tested against exceptions and logic errors. This table is the most commonly used format.
|
Test Number |
Description |
Data type |
Expected result |
Pass/Fail |
Cross Reference |
|
You will describe what the test is looking for and how you will perform it |
This will be Typical, Erroneous or Extreme. If you don't know what this means read below |
How are you expecting the system to respond to your input data? Should it give an error message? Will the response be any different to a normal one? |
Did it succeed or fail? You are aiming for the vast majority to be passes |
link this test to your screen shot that proves it works |
|
|
Eg. #1 |
The average price of all the chocolate bars is calculated on the Choc Form |
typical |
When we have 5 chocolate bars at 20,25,20,25,30 pence the average will be displayed as 24p |
Pass |
See screen shot 2 |
This can be used for database connection data transfers and outputs.
Overall performance against Objectives
Ultimately you will test to see if each of your objectives have been met some will be objective and covered above but some will be subjective and require user feedback (Beta Testing)
Beta Testing
In your strategy, you should say who is going to test your program and using what data. Ideally, you should have a few questions that they will use to give you structured feedback