Contents
How many test cases can be executed per day?
Executives expect answers such as, “We have 500 out of 10,000 test cases remaining,” “On average, we can do 50 test cases per day, so about 10 days,” or, “We are 95% complete.” As those with experience have learned, however, these types of answers don’t always provide the appropriate information.
How do you manage automated tests?
Here are the 5 ways of managing your test automation projects effectively and make the most out of your test automation efforts.
- Plan Your Test Cases & Test Suites.
- Centralize Your Test Assets.
- Differentiate Test Objects.
- Validate & Remove Outdated Test Cases.
- Separate Test Architecture.
How to avoid test cases that are too simple?
First, the test cases might be too simple, meaning they only test the main function without testing too many extreme cases. To avoid this, a developer should cover as many corner cases as possible. If an interface is being developed and requires an input that isn’t trivial, then testing for bad or empty inputs is important.
What happens when you have a lot of test cases?
The tests pile up and when it’s time to do a full regression, the team discover a massive amount of test cases, including duplicate test cases and invalid tests. Usually, there is a small window in which to execute the full regression and now the team must sift through all the tests to figure out which of those to execute.
What happens if your test case repository is too big?
A test case repository can easily grow too large and full of obsolete test cases if not regularly managed. A number of test cases will be executed by QA, reported as failed and then closed by the product owner, to then become an unnecessary waste of time and resources.
How to avoid the most common use cases?
Most developers are easily able to write code for the most common use cases. The problems surface the moment there is a condition of the most common use case. A well-designed test case will catch these easily. 5. Any test case can become completely useless if not cataloged systematically and kept available for use.