At my workplace, we often use a test case matrix to plan out what tests we want to do, which generally looks like a very elaborate decision matrix.
Within my team, I’m the only one who knows how to make them, and I’ve been asked to do a session on how to make it.
My first thought is, what I call a test case matrix might be different to others, so I thought I would say what I’m wanting them to do.
For this scenario, it is working out what tests they would do, for a report that lists all withdrawl requests => £6000. However, if the customer is >= 60, then the threshold is lowered to £3000.
My immediate thoughts are this.
For amount options, there’s six different amounts I would look at:
And then for age options, there’s three I would look at:
- 60 years old -1 day (I wouldn’t say 364 days old, as what about leap years?)
- 60 years old
- 60 years old +1 day
If you times them together, I would get 18 possible tests, of which some I would expect to be on the report, and some not. But would all 18 combinations be needed, or would it be better for them to show them, and then discuss if it is necessary to test to not?
You (and they) might ask, why do three range BVA? Well, how do I know it hasn’t been coded for = £3000 for example, rather than >= £3000?
So the below is a sample of what I would expect them to build, to show if somone should or shouldn’t be shown in the report.
Amount 3000 2999.99 3000.01 Age 60 60 60 On report? Y N Y
Now, if I really wanted to curveball them and raise the difficulty, I would get them adding another layer which is what if there is more than one person on the account? And then all are below 60, all above 60, and one is below 60 and one isn’t?
If I gave you the above scenario, would you have ended up with 18 combinations?
Would you even use a matrix, or do something else, like a flow chart to look at combinations instead?
Are there even more things that I’m missing and should be mentioning?
Do you even use a matrix such as this to work out your tests?