Number of Test Cases Automated Per Day
This is a common experience-based interview question. The honest answer depends on complexity.
Typical ranges:
Simple test cases (2-5 per day):
- ✓Basic form validation tests
- ✓Simple navigation tests
- ✓CRUD operation tests
- ✓Login/logout flows
- ✓Standard dropdown selections
Complex test cases (1 or fewer per day):
- ✓Multi-step checkout flows
- ✓Dynamic data-driven test setup
- ✓New page object class creation
- ✓Framework enhancements
- ✓Cross-browser configuration
- ✓Integration with external APIs or databases
Factors affecting the count:
| Factor | Impact |
|---|---|
| Test complexity | High complexity → fewer tests |
| Page Object creation needed | New POM = extra setup time |
| Test data setup | Database seeding takes time |
| Debugging time | Flaky locators, timing issues |
| Framework work | CI integration, reporting setup |
| Documentation required | Writing test plan, updating JIRA |
Real-world example answer:
"It depends on the Test case scenario complexity and length. I automated 2-5 test scenarios per day when the complexity is limited. Sometimes just 1 or fewer test scenarios in a day when the complexity is high — for example, creating a new Page Object class with @FindBy for a complex form, setting up @DataProvider with Excel reading, or configuring new Selenium Grid nodes."
Quality over quantity: The more important metric is test effectiveness — a well-structured, maintainable test is better than 10 fragile ones. Tests should:
- ✓Be independent
- ✓Be reusable via POM
- ✓Have clear assertions
- ✓Be maintainable when the UI changes
Key answer: It depends on complexity. Generally 2-5 test scenarios per day for limited complexity, and 1 or fewer per day when complexity is high.