Should I include negative test scenarios in my test automation? As of now, I'm just using positive tests for my test automation. Any ideas from you are pretty much appreciated.
Thanks in advance. Cheers!
What does your product manager say?
Your product owner (aka stake holder) will be interested in listening to your reason for having positive tests and negative tests or not. You may need to present the pros and cons to your product owner to help him / her make this decision. Some of aspects you may need to take into account include but not limited to:
Please remember a tester is an integral part of a multi-discipline, cross-fucntional team. Your decision should never be made alone, please coordinate with the rest of your team before making a decision that may impact others and mostly importantly, the overall progress of a project.
Negative scenarios "expected errors" should be commonly checked as well as positive scenarios. The expected error handling is a part of software and an important part of user guidance in software usage.
E.g. user could enter wrong password or login that could not be saved, but the user should be normally notified by the system what he has done wrong. And keep in mind that boundaries of negative cases are usually much bigger than positive ones, so you should work with values close to boundaries on negative sides or even use randomization in some cases.
Automation of negative cases are highly expected when:
Here some cases when you should not automate negative cases:
Agree with all other answers. I suggest to pitch to include negative scenarios.
When one is taking decision to implement automation for any application, it's rare that it would have less time frame which will restrict you from implementing negative tests
Using automation we have some boundaries already limited to identify bug/defect[As a result can not automate 100% all manual test cases], So if we exclude negative scenarios also then we might not be able to use max power of automation
Yes, surely you need to communicate this to senior team members and stakeholders for clarity if you focused & concerned on ROI[return on investment]