QTP - Chapter I

                                                                                                                                                                                                                                                                                                                                                      Introduction of Automation

Testing: - Testing is the process of improving the quality of software.

    Ways to testing: -

•      Manual testing
•      Automation testing

Manual Testing: -

It is a process where we complete all the phases of STLC (software testing life cycle) by manual, is called
as manual testing

Draw backs of manual testing: -

• Time consuming
• More number of human resources are required
• Tiredness of the testers
• Human errors (Less accuracy)
• Simultaneous actions are almost impossible

Automation Testing:-

Automation testing is a process where we can test the application with the help of Automation Tool

Benefits of Automation Tool:-

•  Fast: - It runs the script faster than human beings.
•  Reusable: - We can reuse the scripts in different regression testing.
• Cost reduction: - It reduces number of resources and hence less budget.
• Accuracy: - No tiredness and hence good accuracy results.

Disadvantage of Automation Testing:-

• Proficiency is required to write automation test scripts.
• It is expensive to buy.
• In all areas automation testing is not possible.

Difference between Manual and Automation Testing:-

Manual Testing:-

1. Testing is implemented by manually 
2. 2. It is the best suite for application which the numbe of test cycles are less
3. The test case development is less
4. The test case execution time is more
5. The test data needs to be provide by manually
6. The test reports can be generated by manually
7. Defects need track manually
8. Organization point: the cost of manual testing is more
9. The programming knowledge is optional

Automation Testing:-

1. Testing is implemented by using tools
2. It is the best suite for application which number of test cases less
3. Test script development time more
4. Test script execution is time is less
5. The test data can be generated by tool it self
6. The test cases can be generated by automatically
7. Defects can be tracks automatically
8. the cost of automation testing is more
9. A minimum programming knowledge is required

Types of testing can be done by Automation: -

•  Functional (Positive and Negative) testing
• Regression Testing
• Performance Testing
• Usability Testing

Functional Tools:-

• Quick Test Professional (QTP)
• IBM rational functional tester
• Winrunner
• Selenium
• Test complete

Performance tools:-

• Load runner
• J meter
• Test complete

Test Management Tools:-

• Test direct
• Quality center
• Bugzilla
• Rally
• Clear quest

Things to done before Automation Testing: -

1. Return on investment (ROI)
2. Tool selection
3. Identify Framework
4. Automation feasibility

Automation feasibility: -

It is a process of identifying what test case can be automated and cannot be automated.

This will be done by automation tester for their respective modules.

What test case can be Automated: -

• The test case needs to be run on every build
• The test case needs to be run on multiple test data
• Multiple browser compatibility test cases
• Application objects which do not change in short time

What test case cannot be Automated: -

• Security related test cases
• Idle time functionalities
• Batch processing requirements
• Graphs related test cases
• Usability test cases
• Documentation verification testing
• 3rd party objects requirements. Ex: - PDF, Printers etc...

> After completion of Automation feasibility we go for estimations

Example: - Finding number of resources to automate for 800 test cases in 100 days

• Number of test cases to designed per day = 800/100=8 test
• One resource 2 scripts per day
• How resources need if 8 scripts per day =8/2=4 resources

Example: - Finding number of days to automate 800 test cases with 4 resources

• One resource 2 scripts/ day
• 4 resources 4*2=8 scripts/day
• Number of days = Total test cases/per day scripts= 800/8=100 days

Automation testing process: -

1. ROI [Return on Investment]

2. Tool selection

3. Test cases feasibility analysis

4. Preparation of automation test plan document

5. Framework designing

6. Designing test scripts for manual test cases

7. Involve in code walkthroughs and code inspections

8. Test scripts debug

9. Involving in regression support by executing test scripts as a batch
10. User acceptance testing

                                                                                                                                                   

                                                                                                                                          

                               **** End of Chapter I ****