Testing Presented By, Christy Premkumar

What is Software Testing?

Software Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements or identify differences between expected and actual results.
Software Testing is important as it may cause mission failure, impact on operational performance and reliability if not done properly.

Ways of Testing

Manual Testing
Manual testing is performed by the tester who carries out all the actions on the tested application manually, step by step and indicates whether a particular step was accomplished successfully or whether it failed.
Manual testing is especially useful in the initial phase of software development, when the software and its user interface are not stable enough, and beginning the automation does not make sense.

Benefits of Automation

Automation Vs Manual Testing

Pros of Automation If you have to run a set of tests repeatedly, automation is a huge win for you. It gives you the ability to run automation against code that frequently changes to catch regressions in a timely manner. It gives you the ability to run automation in mainstream scenarios to catch regressions in a timely manner . Aids in testing a large test matrix (different languages on different OS platforms). Automated tests can be run at the same time on different machines, whereas the manual tests would have to be run 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.

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 the feature, 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.

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.

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.

Valid Descriptive Programming

Example 1 You 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 run session MyVar = some text string Browser(Hello).Page(Hello).WebTable(table).WebEdit(name:= &MyVar)

Example 2 The Statement below specifies a WebEdit test object in the Mercury Tours Page with the Name author and an index of 3. During the run session, Quick Test finds the WebEdit object with matching property values and enters the text Mark Twain. Browser(MercuryTours).Page(MercuryTours).WebEdit(Name:=Author , Index:=3).Set Mark Twain

Example 3 You can use the following statement since it uses programmatic descriptions throughout the entire test object heirarchy: Browser(Title:=MercuryTours).Page(Title:=MercuryTours).WebEdit(Na me:=Author, Index:=3).Set Mark Twain Example 4

You can use the statement below, since it uses programmatic descriptions from a certain point in the description (starting from the Page object description):
Browser(MercuryTours).Page(Title:=MercuryTours).WebEdit(Name:=A uthor, Index:=3).Set Mark Twain

Invalid Descriptive Programming

You cannot use the following statement, since it uses programmatic descriptions for the Browser and Page objects but then attempts to use an object repository name for the WebEdit test object: Example Browser(Title:=Mercury Tours).Page(Title:=Mercury Tours).WebEdit(Author).Set Mark Twain QuickTest tries to locate the WebEdit object based on its name, but cannot locate it in the repository because the parent objects were specified using programmatic descriptions.