This blogpost is a follow up of “Beyond Test Cases” that I did a few days ago.
When I say I certainly do want to write test cases but still want to save as much time as possible, it must be backed up with convincing ways/tricks.
So, here are few things which I have tried, read about & want to try (the list is ever evolving):
1. The simplest one is to still write high level test cases but strip off all the redundant information. This is illustrated in below example:
Lets take up login page functionality with 3 scenarios:
I have safely omitted details which are obvious.
2. How about applying the test Design techniques that we learn for exams and certifications. Recently I had to test a piece of functionality where combination of multiple inputs would result in different multiple output conditions. Writing Test cases for such a thing does need time and in case you need to revisit them for modification, it can be a nightmare.
Alternatively, I chose to do just a decision table as shown below:
Each column in the table is one test case. It’s quick to create, easy to understand and a breeze to modify.
3. Mind Maps: Its always to remember anything which you can visualise. Mins Maps are a great way. If you are pressed for time, test scenarios can be represented as a mind map. Take a printout and start testing. Mind Maps can be used to present any kind of information. Have a look at some cool mind maps here.
4. Tree Diagrams : This is yet another way of representing scenarios which have multiple child conditions and you need to use different input combinations. It’s really quick when you it on a paper rather than using a software. I have used Tree Diagrams as preparation work for writing test cases and it helps ensuring nothing is missed.
5. Checklists: Checklists are great for something like usability testing which has endless things to test. It makes more sense to jot them down as bullet points and tick them off during execution.