Automated Testing Gireendra Kasmalkar Prabodhan Exports Pvt. Ltd.

Need for Automated Testing u Automation ensures implementation of process u Repetitive testing u Simulated testing u Voluminous data testing u Internal testing

Types of Automated Testing u Component u Regression u Load u Web-site checking u Memory Leak u Coverage

Automated testing for products / projects u For products –Regression u For projects –Data preparation u For web-sites –Navigation u For all –Load / Performance –Memory Leak –Coverage –Component

List of tools u Mercury Interactive (Winrunner, LoadRunner, Astra Site Manager) u Segue (SilkTest, SilkPerformer) u Rational (Test Studio incl. Robot and Pure) u Empirix (E-Suite) u Microsoft (Web Application Stress Tool) u Cyrano (OpenSTA) u Building your own tools –For components and systems –Need for planned and centralized approach –Can be very efficient and effective

GUI-based Automated Regression Testing u Misconceptions –Easy to build – simple record and playback –Very little effort –Replaces manual testing –Testing can be completely automated u Objectives –Regression testing – to verify that things still work –Routine testing – to allow expert resources time for more critical testing –Repeated testing – reuse over a number of builds and releases

Requirements from Automated Regression u Robust u Data-driven u Maintainable

Process for Automation Development u Tool Evaluation u Analysis (Feasibility) u Design u Development u Testing u Deployment

Elements of Automated Regression u Test script u Test data u Test report u Design and architect for robustness etc.

Elements of a Test Script u Action u Verification u Report u All good programming practices

Prerequisites for automation u Stability of application u Test cases must be ready u Knowledge of tool

Limitations in Automated GUI Testing u Testing Compatibility u Testing Robustness u Testing Usability

Load / Performance Testing u Misconceptions –A tool is all that is required –Problems are directly identified –Extrapolation of results is possible –Has to be done on production setup u Objectives –Benchmarking –Identifying limits –Stability –Bottle-neck finding

Process for Load / Performance Testing u Tool Evaluation u Requirement u Analysis u Planning and setup u Development of scenarios u Execution u Analysis & Report

Elements of a Load Testing Scenario u Transaction u Workload u Server side configuration u Network bandwidth simulation u Output parameters

Prerequisites for Load / Performance testing u Functional stability of application u Knowledge of tool u Collaboration with developers –Criticality of scenarios –Tuning parameters e.g.connection pool –Understanding logs

Setup u Isolated network u Client machines u Specified server configuration

Execution u Execute scenario with ramp-up u Monitor –Server –Network –Client u Data collection u Analysis u Rerun

Conclusion u Very important and effective components of the total testing effort u Objectives must be clear and realistic u Requires tools, specialized skills and processes u Requires dedicated and planned effort