Hi all,
So, I recently missed a bug that slipped into production - we had made a change to the validation on a web page and it caused an adverse knock-on affect to the validation behaviour. When I reviewed my test plan and regression pack I realised that I didn’t actually have any test cases in places that could have caught this particular bug, which got me thinking:
How about in addition to my high level regression test cases I also come up with ‘mini regression’ cases for each area, for example: validation - I would have an exhaustive list of things to check for this area, including:
• Special characters
• Long string
• Empty
• Spaces
• Numeric/alphanumeric
• Numeric variables (commas, decimal places, leading zeros, negative numbers, )
• Trigger validation by leaving fields blank – when completing fields ensure that validation messages disappear
Before I go down this path, does this seem like a good idea or is there a better way I could do this?
I am currently trying to think of as many key areas for testing websites as possible. At the moment I’ve got:
• Validation
• Fields
• Text
• Links
• CSS/styling
• Buttons
I’m sure there will be lots more! The idea would be to maintain this regression pack and only pull in the relevant ones I require for each project, eg: if we have changed the CSS then I would run that regression.
Thanks,
sad_muso