Automation Testing - Christy Premkumar

8/2/2019 Automation Testing - Christy Premkumar

1/13

Testing

Presented By,

ChristyPremkumar


2/13

What is Software Testing? Software Testing is a process of evaluating asystem by manual or automatic means and verifythat it satisfies specified requirements or identifydifferences between expected and actual results.

Software Testing is important as it may causemission failure, impact on operational performanceand reliability if not done properly.


3/13

Ways of Testing


4/13

Manual Testing Manual testing is performed by the tester whocarries out all the actions on the tested applicationmanually, step by step and indicates whether aparticular step was accomplished successfully or

whether it failed.

Manual testing is especially useful in the initialphase of software development, when the softwareand its user interface are not stable enough, and

beginning the automation does not make sense.


5/13

Benefits of Automation


6/13

Automation Vs Manual TestingPros of Automation

If you have to run a set of tests repeatedly, automation is a hugewin for you.

It gives you the ability to run automation against code thatfrequently changes to catch regressions in a timely manner.

It gives you the ability to run automation in mainstream scenariosto catch regressions in a timely manner .

Aids in testing a large test matrix (different languages on differentOS platforms). Automated tests can be run at the same time ondifferent machines, whereas the manual tests would have to berun sequentially.

Cons of Automation It costs more to automate. Writing the test cases and writing or

configuring the automate framework youre using costs more

initially than running the test manually. Cant automate visual references, for example, if you cant tell the

font color via code or the automation tool, it is a manual test.


7/13

Automation Vs Manual Testing

Pros of Manual If the test case only runs twice a coding milestone, it most likely

should be a manual test. Less cost than automating it. It allows the tester to perform more ad-hoc (random testing). In my

experiences, more bugs are found via ad-hoc than via

automation. And, the more time a tester spends playing with thefeature, the greater the odds of finding real user bugs.

Cons of Manual Running tests manually can be very time consuming Each time there is a new build, the tester must rerun all required tests -

which after a while would become very mundane and tiresome.


8/13

Introduction to Descriptive Programming

Descriptive programming is used when we want to perform an operation

on an object that is not present in the object repository. There can be

various valid reason to do so. We will discuss them later in this article.


9/13

How to write Descriptive Programming

There are two ways in which descriptive programming can be used

1. By giving the description in form of the string arguments.

2. By creating properties collection object for the description.


10/13

Valid Descriptive ProgrammingExample 1You can enter a variable name as the property value if you want to find

an object based on the property values you retrieve during a runsession

MyVar = some text string

Browser(Hello).Page(Hello).WebTable(table).WebEdit(name:=&MyVar)


11/13


12/13

Example 3

You can use the following statement since it uses programmatic descriptionsthroughout the entire test object heirarchy:

Browser(Title:=MercuryTours).Page(Title:=MercuryTours).WebEdit(Name:=Author, Index:=3).Set Mark Twain

Example 4

You can use the statement below, since it uses programmatic descriptions froma certain point in the description (starting from the Page object description):

Browser(MercuryTours).Page(Title:=MercuryTours).WebEdit(Name:=Author, Index:=3).Set Mark Twain


13/13

Documents

Automation Testing - Christy Premkumar