Test Automation
Download as PPT, PDF0 likes128 views
Automation testing replaces or supplements manual testing by using test programs to simulate user actions. It reduces testing time and costs by running tests consistently and repeatedly. While it has upfront costs, automation saves substantially over multiple product releases. Not everything can be automated, like visual references, so some tasks still require manual testing. Tests should be automated if they are repeatable and important to run regularly, even if automation has some initial costs. The document provides an example of test automation using Quick Test Pro 8.0 for modular scripting and version control with reporting in Excel.
Test Automation
- 2. Quick Glance • What? • Why? • How? about Automation Testing • Automation used in BCC6.0 • Demo
- 3. What? • Test automation is used to replace or supplement traditional manual software testing with a suite of test programs. • Test automation is a technique to simulate user actions.
- 4. Why? • Reduce Testing Time – A typical automated test will run in less than 24 hours. For a sophisticated product manual testing may require dozens of staff months. • Consistent Test Procedures – With a complex testing process manual testing may/often yield/s inconsistent coverage and results depending upon the staff and schedule employed. An automated test suite ensures the same scope and process is used repeatedly each time testing is performed. • Reduced QA Cost – Automated testing has an upfront cost to develop. But over the lifetime of a product it will offer substantial net saving. An average automated test suite development is 3 to 5 times the cost of a complete manual test cycle. Over multiple product releases with multiple cycles per release, this cost is quickly recouped. • Improved Testing Productivity – With it’s much shorter execution time an automated test suite can be run multiple times over the course of product/ application development. • Improved Product Quality – Automated testing detects functional and performance issues more efficiently.
- 5. Automation Pros & Cons • If you have to run a set of tests repeatedly, automation is huge win. • It gives us the ability to run automation in mainstream scenarios to catch regressions in a timely manner. • Aids in testing a large test matrix. • Automated test cases can be run at the same time on different machines whereas manual tests would have to be run sequentially • It costs more to automate. • Writing and configuring framework require more costs initially than running the tests manually. • Can not automate everything e.g. Visual references (if you can not tell the font color via code or tool, it’s manual test)
- 6. How? • What to automate? • When to automate? Do you think these are the very quick questions that come to your mind when you are about to start automation ?
- 7. Criteria for Automating Now ask yourself two question. • Is this scenario Automatable? Yes, and it will cost a little. Yes, but it will cost a lot. No, It is not possible to automate. • How important is this test scenario? I must absolutely test this scenario whenever possible. I need to test this scenario regularly. I only need to test this scenario once In a while.
- 8. • If u answered #1 to both questions - definitely automate that test. • If u answered #1 or #2 to both questions – you should automate that test. • If u answered #2 to both questions – you need to consider, if it’s really worth the investment to automate.
- 9. What happens if you can not automate? Say you answered #3 and #1 respectively to both questions!!!!!!!!!!!!! • Re-evaluate. Do I really need to run this test often? • What is the cost of doing this test manually? • Look for new testing tools. ....you can not do anything else.
- 10. Automation in BCC 6.0 • Automation Tool: Quick Test Pro 8.0 • Scripting Technique: Modular Scripting • Reporting (Automation scripts Results) : Ms Excel • Version Control: Surround SCM
- 11. Demo • This is a scenario in which Create Technology is being performed involving various a Error and Alternative scenarios.
- 12. Thanks