Thursday, 16 January 2014


J Automation Testing Approach for a project J
Process flow:
*      Feasibility study: After getting a new project the automation test manager will perform feasibility study to check the project is acceptable or not for automation testing.
        While analyzing, the test manager will consider the following factors…
*                  Complexity of application functionalities
*                  Application environment
*                  Return on Investment
*                  Time feasibility
*      Selection of Automation Tool: If the project is acceptable after feasibility study, the test manger will select the automation tool they are going to use by keeping the following points in mind,
*                  Supporting tool of application environment.
*                  Availability of resources (Like tools and automation test engineers).
*                  Is client specifying any particular tool for automation or not???
*      Prepare Test Strategy/Framework: Once the tool selection is done the test manager prepares the Test Strategy/Framework design based on application functionalities.
Test Strategy/Framework describes the set of activities need to be followed to develop the test     scripts using available resources.
*      Prepare Automation Test Plan Document: Based on the framework design test lead prepares automation test plan document.
        Test Plan document will describes the details of selected resources for automation , training needs, schedules, deliverables, etc…
*      Developing Automation Test Scripts:  Based on the test scenarios Automation Test scripts will be generated by the automation test engineers once the automation test plan document gets approved.
*      Execution & Maintenance:  Once the test engineers complete generating test script they will run the scripts and analyses the actual result with expected results and then defect report sheets are prepared.
Maintenance is the big thing in the entire automation testing for future purpose, to reuse the test scripts and resource files later specific folder structure is used to store the files.

Main folder                                                        Sub Folders
                                                                                                Actions
                                                                                                Environment
                                                                                                Library Functions
Project Name                                                              Test Data
                                                                                                Recovery Scenarios
                                                                                                Test Log/Result
                                                                                                Repositories

Simple technique to remember
Feasibility study à Tool Selection à Test Strategy/ Framework Design à Test plan doc. Preparation à Test Scripts à Execution and Maintenance J













J Introduction of Automation Testing J
What is Automation Testing???
Automating the human activities in order to validate the application functionalities within less time (when compared to manual testing approach) is known as Automation Testing.
Application is validated with the help of either third party automation tools or scripting and programming languages.
Example of third party automation tools -> Quick Test Professional (QTP),  Selenium, Rational Robot, Win Runner , etc…
Why should we opt for automation testing???
*      Fast in execution.
*      More reliable.
*      More consistent.
*      Test script is repeatable so we can validate the functionalities with multiple set of data.
*      And script is reusable for different similar type of applications and on different versions.

Are there any drawbacks of opting for automation testing???

Yes, Of course. L For every technology we have drawbacks, similarly for opting this method also have drawbacks (disadvantages).

*      Automation tools are expensive.
*      Skilled automation test engineers are required.
*      Some parts of the functionalities are not possible to automate.
*      Automation tools support only some kinds of environments. (Example: QTP supports only windows operating systems).

So it is very clear that we cannot opt for automation in all the scenarios. Then, in what cases we should choose this automation testing.

Scenarios which can be preferred to automation testing…J

The scenarios which are more repeatable and complex to validate the functionalities manually is suitable for automation testing.
Example: When we perform retesting and regression testing, we can opt for automation testing.
                If the scenarios are not repeatable and easy to perform manually then we will be continuing with manual testing.
Example: User Interface testing, usability test scenarios, one time testing activities, adhoc testing, etc…

Wednesday, 15 January 2014

Hi Amigos!!

Welcome to my new blog Automation with QTP...

I created this blog for the reference of all the concepts and test scripts.
I will do testing instead of you because of  less time...Just guide me in a correct procedure