Selenium for Automation Testing
------------------------------
Introduction to Automation Testing:
-----------------------------------
S/w Testing:
It is a combination of Verification and Validation
S/w testing will help to identify defects, when those are resolved then S/w quality improves
S/w Testing methods:
there are 2 types of approaches to validate applications
1. Manual Testing:
2. Automation testing:
1. Manual Testing:
Without using any automation tool TE directly interact with application to verify actual behavior while performing
operations is called manual testing
for manual testing we prepare test cases and those are used to validate application
Advantages:
-It is simple and easy to perform for small projects
-less cost compare to automation testing for small projects
Disadvantages:
-Time consuming
-Inconsistency (Focus)
-Lack of Reliability (Human Errors)
2. Automation Testing:
Any task or activity performed with help of tool/programs is called Automation
ex: Using Calculator to find multiplication of values is an example for Automation
**Automating human activities (i.e. Test Execution) in order to validate application is called Automation testing
Automation testing can be performed using programming languages (eg., C#) or scripting languages (eg., Perl script) or
using any one of the 3rd party automation tool like Selenium/QTP/Test Complete, etc.,
For Automation Testing we need to develop the automation test scripts
Advantages:
-Fast in Execution
-More Consistency
-More Reliability
-Automation test scripts are Reusable
-Automation test scripts are repeatable
Disadvantages:
-Automation testing is an expensive
-Skilled Automation TE's are required
-Some Technologies/Environments are not possible to automate
Selection Criteria for a project to perform Automation testing:
--------------------------------------------------------------
Following are the factors they check to confirm project is suitable for automation testing or not
-More resource required and time consuming to validate application
-Multiple Releases are expecting
-Application Environment supports automation tools
-Avilable budget
Some of the Common activities during Manual testing and Automation Testing:
-------------------------------------------------------------------------
1. Manual Testing:
Identify Test SCenarios
prepare test cases
perform test execution
Defect Reporting
Getting them fixed
2. Automation Testing:
Identify Automation Test scenarios
Develop the automation test scripts
Execution of Test scripts
Analyze results
Defect Reporting
Getting them fixed
============================================================================
SCenarios which are prefered for Automation testing:
In general scenarios which are complex to perform manually and more repeatable those are more suitable for
Automation testing
ex:
Build Verification Test Scenarios(BVT)
Re-Testing Scenarios
Regression Test Scenarios
Scenarios which are not preferable for Automation testing:
Scenarios which are not repeatable and easy to perform manually those are not suitable for automation testing
ex:
GUI Test Scenarios {Cosmetic, Look-N-Feel of the application}
Usability Test scenarios {User friendlyness/Ease of use}
One time testing activities
Informal testing activities such as exploratory testing, smoke testing, sanity testing etc.,
Note: For one project, there can be Manual testing team and Automation testing team, for some of the
projects Automation testing is an optional
Note: In general, Automation test scripts are designed/developed only once a stable build is available
------------------------------
Introduction to Automation Testing:
-----------------------------------
S/w Testing:
It is a combination of Verification and Validation
S/w testing will help to identify defects, when those are resolved then S/w quality improves
S/w Testing methods:
there are 2 types of approaches to validate applications
1. Manual Testing:
2. Automation testing:
1. Manual Testing:
Without using any automation tool TE directly interact with application to verify actual behavior while performing
operations is called manual testing
for manual testing we prepare test cases and those are used to validate application
Advantages:
-It is simple and easy to perform for small projects
-less cost compare to automation testing for small projects
Disadvantages:
-Time consuming
-Inconsistency (Focus)
-Lack of Reliability (Human Errors)
2. Automation Testing:
Any task or activity performed with help of tool/programs is called Automation
ex: Using Calculator to find multiplication of values is an example for Automation
**Automating human activities (i.e. Test Execution) in order to validate application is called Automation testing
Automation testing can be performed using programming languages (eg., C#) or scripting languages (eg., Perl script) or
using any one of the 3rd party automation tool like Selenium/QTP/Test Complete, etc.,
For Automation Testing we need to develop the automation test scripts
Advantages:
-Fast in Execution
-More Consistency
-More Reliability
-Automation test scripts are Reusable
-Automation test scripts are repeatable
Disadvantages:
-Automation testing is an expensive
-Skilled Automation TE's are required
-Some Technologies/Environments are not possible to automate
Selection Criteria for a project to perform Automation testing:
--------------------------------------------------------------
Following are the factors they check to confirm project is suitable for automation testing or not
-More resource required and time consuming to validate application
-Multiple Releases are expecting
-Application Environment supports automation tools
-Avilable budget
Some of the Common activities during Manual testing and Automation Testing:
-------------------------------------------------------------------------
1. Manual Testing:
Identify Test SCenarios
prepare test cases
perform test execution
Defect Reporting
Getting them fixed
2. Automation Testing:
Identify Automation Test scenarios
Develop the automation test scripts
Execution of Test scripts
Analyze results
Defect Reporting
Getting them fixed
============================================================================
SCenarios which are prefered for Automation testing:
In general scenarios which are complex to perform manually and more repeatable those are more suitable for
Automation testing
ex:
Build Verification Test Scenarios(BVT)
Re-Testing Scenarios
Regression Test Scenarios
Scenarios which are not preferable for Automation testing:
Scenarios which are not repeatable and easy to perform manually those are not suitable for automation testing
ex:
GUI Test Scenarios {Cosmetic, Look-N-Feel of the application}
Usability Test scenarios {User friendlyness/Ease of use}
One time testing activities
Informal testing activities such as exploratory testing, smoke testing, sanity testing etc.,
Note: For one project, there can be Manual testing team and Automation testing team, for some of the
projects Automation testing is an optional
Note: In general, Automation test scripts are designed/developed only once a stable build is available