Frequently Asked Question to QA Team

When Dev Team Takes 1 Day for Development, Why Does Test need 2 Days for Testing

• Development involves Design, Coding, Unit Testing, Release
• Quality of Development Deliverables can be measured by Bugs found in Test
• Quality of Test Deliverables can be measured by Bugs found in Production
•  With Pure black box testing, possibilities of reducing test estimates may prove risky
• With a mix of black box and white box testing, You can take a calculated risk of Areas of Scope (Must be covered) Vs Sanity Testing in other Areas
• Estimates should be looked at what are the areas covered in testing, Comparision of Development and Test Estimates is *NOT a* valid argument

1 Line of Code Change, Why Do you need 1 Day for Testing ?

Most common question for Test Team. What it takes to Deliver it by XX-XX-XXXX Date ?

Can we cut down Test Estimates by 1 Day ?

• Estimates should be looked to analyze Tasks Covered, Scope of Testing, Percentage of Test Automation in place. 
• With a mix of black box and white box testing, You can take a calculated risk of Areas of Scope (Must be covered) Vs Sanity Testing in other Areas

Why Automation did not catch this bug ?

• Domain expertise comes with experience and exposure. Good Testers have very good domain knowledge of product
• Obvious bugs# can be caught by automation. Layout related / Integration issues would be caught during manual exploratory testing
• Automation plus manual exploratory testing would be good approach to maintain high Quality product

We need 100% Automation

• Building automation framework before product lauch and Priority 1 cases Automation before product release is a good approach dealing with automation
• Based on events captured in production, User Workflows need to converted into equivalent integration scenarios to simulate end user scenarios
• From the production bugs# keep enhancing the Automation suite

Happy Reading!!