Test Automation August 17, 2007
© ThoughtWorks, 2007
Objective – What Test Automation means – When to Automate & Best practices used – See how Automation Tools work
© ThoughtWorks, 2007
What is Test Automation ? • A piece of software program written to reproduce the steps/actions defined in a manual process.
© ThoughtWorks, 2007
Why Do we need Test Automation ?
– Speed up testing to accelerate releases – Allow testing to happen more frequently – Improve test coverage – Ensure consistency
© ThoughtWorks, 2007
Few Examples 1. If I want to create 100 users, which involves entering 10 different values in a user registration page, it makes more sense to write a small script to do this. 2. If I want to execute 10 test cases everyday for next 3 months, then it makes more sense to write a small script for this.
© ThoughtWorks, 2007
When to Automate a Test ?
• Automate relatively stable functionalities which require repeated testing.
© ThoughtWorks, 2007
Automation Workflow
© ThoughtWorks, 2007
Various Automated Testing Tools used for different Testing Types
• Unit Testing – NUnit, JUnit • Functional Testing – Sahi, QTP • Performance Testing – JMeter, Load Runner
© ThoughtWorks, 2007
Automation Tool Demo
© ThoughtWorks, 2007
Automation Best Practices
– Choose a test tool that best fits the testing requirements of your organization. – Only automate those tests that are going to be repeated. – Before starting off with Test Automation, identify the test cases that can be automated. – Automate the majority of your tests, which are fairly straightforward. – Use a data-driven automated testing methodology. © ThoughtWorks, 2007
Questions?
© ThoughtWorks, 2007