FAQs Archive - Page 33 of 34

Q: Should I focus my resources purely on automating?

Automation is just one weapon in the QA armory. We recommend a nuanced approach: supplement automated testing with other QA approaches including planning, manual and crowd testing, user and accessibility testing. We recommend looking at the whole, not just focusing on automation alone.

Q: Should I automate everything?

No. Only automate stable entities with repeatable actions. Choose cases where there isn’t much change, to avoid higher maintenance costs and gaps in automation coverage.

Q: Should I keep my automation resources separate from the rest of QA?

No. We recommend fully integrating them with the whole QA team. Ideally, use the same team for automation and crowd testing, so they’re governed by one QA process.

Q: Should I track what’s being automated and what isn’t?

Yes. As well as knowing what’s being automated, you need to know the coverage achieved. That way you can identify what you need to test by other means.

Q: My test automation framework is getting overengineered. How should I identify when to automate and when not to?

At Digivante we create the very best manual test cases and coverage. They form the building blocks for good automation. These will show clearly whether it’s beneficial to automate or not.

Q: I have a consultant building automation for me so why would I need to use an outsourced testing company?

It depends how thorough the consultant can be. Just one person can’t usually do it all! At Digivante we’re transparent on the framework we use and how we build the scripts. We make clear which tests are automated, crowd or manual. We provide clear documentation and training for internal staff.