When you’re testing a new feature on an app or website, it’s considered a best practice to have test cases. Ideally, the tester will be given acceptance criteria for the feature being developed. When QA knows exactly what a feature should or shouldn’t do, writing test cases can be easy enough. (If you’re feeling lost, see our article explaining test cases.) But how do you write test cases without requirements?
After all, in the real world of a fast-paced Agile process, chances are you won’t always have them. It’s pretty common to encounter a Jira ticket with a simple description, and no real list of requirements. Sure, you could ask the person responsible to add them. But it’s not always clear who that should be. (The developer? Project manager? Product manager? Higher up?)
In many scenarios, the task can get passed back and forth so long, it delays the testing process by days – if you even end up getting requirements at all. Continue reading →
Manual Testing
Some companies use 100% manual testing to great success. Others have attempted to do 100% automation, and had to re-think their strategy — so the reality isn’t always as black and white as it may appear.