Integrating Automation into Manual Testing automation WILL NOT replace manual testing

Why Automation? Automation is the best way to increase the effectiveness, efficiency, coverage of testing, and higher quality Benefits of automation Reusability on smoke tests, regression tests Preparing test data Complex business logics Cross platforms (different OS, browsers, etc.) Execute in numbers of iterations Candidates of Automation Select the correct test cases to achieve higher Return On Investment There are no standard procedures for determining the correct test cases for automation. It depends on the application you are testing

Where do we start for automation Testing? Understand not every software development project is able to achieve efficient automation Stable products Factors to consider before starting an automation project Why do we want to automate? Which tests should we automate? When should we do it? Who should create/execute automated tests? How should we automate these tests?

Why do we want to automate? Increase effectiveness Increase efficiency Increase coverage of testing Increase higher quality Reusability of testing

Which tests should we automate? Choose the type of Framework to Develop Automation (Data-driven, Modularity-driven, Keyword-driven, Hybrid, Model-based, Code driven, Behavior driven testing) Success of Automation Project is based on success of Manual Testing Project Not all of the test cases can be or need to be automated Test cases take too long to automate between releases – areas change a lot between release Details in the following 5 slides

Select correct test cases for automation Testing Step 1 Identify the factors in below: Test case executed with different set of data Test case executed with different browser Test case executed with different environment Test case executed with complex business logic Test case executed with different set of users Test case Involves large amount of data Test case has any dependency Test case requires Special data

Select correct test cases for automation Testing Step 2 Break each application into modules, identify which modules can be used for automation TC Id Description With different set of data? Different browser Different environment Complex business logic Different set of users Involves large amount of data Any dependency Requires Special data Candidate for automation Comments TC01 abc Y N TC02 TC03 TC04 TC05 TC06

Select correct test cases for automation Testing Step 3 – Combine and group the number of test cases for each module Module No. of TCs with different set of data No. of TCs with different browser No. of TCs with different environment No. of TCs with complex business logic No. of TCs with different set of users No. of TCs with involves large amount of data No. of TCs having dependencies No. of TCs with requires special data Times (in mins) to execute manually Mod1 3 2 180 Mod2 x Mod3 Mod4 Mod5 Mod6

Select correct test cases for automation Testing Step 4 – Summary Name of Module Total number of test cases to Automate Times required to execute manually Time to run using automation scripts Mod1 19 5 1.5 Mod2 x Mod3 Mod4

Determine Factors of deterring the ROI Purchasing and licensing cost of the tool Time to develop the scripts Time to maintain the scripts. Time to analyze the results manually and automatically Time and cost to train the resources. Management overheads

When should we do it? User Story Design and Development are completed User Story Manual Testing is done Defects all fixed Test Cases all passed Automation is ready to start

Who shall create/execute automated tests? Basic Rules: Treat Manual and Automation Team as Independent Teams Manual and Automation team must work together Each team complements of each other even with different skills sets To produce better results they must work together in a unified approach Dev Tester – User Story/UAT QA Architect – Feature/Functionality Test Level Automation Developer –Automation Development Feature Test Level

How should we automate these tests? Select the right automation tool to automate manual test cases into automation tool Software Testing Tools: Free software testing tools(Checkstyle, RIPS,Tao) Graphical user interface testing (Ranorex, SilkTest, Selenium, HP WinRunner, TestComplete) Load testing tools(HP Load Runner, Load Testing, WebLOAD) Security testing tools(AddressSanitizer, Metasploit, Project) Unit testing frameworks(Parasoft, Selenium, Test::More, Jtest, Junit, Xunit, Xunit.net)

Automation High Maintenance Automation requires high maintenance Maintenance is critical All tests must be maintained and passed Rules: Run all tests and results are passed before check in new automation code Fix all automation failures – defects, infra issues, functional changes Constantly tuning and improving automation methodology, frameworks, test cases