Software Testing

Testing

noreply@blogger.com (Unknown) — Mon, 29 Sep 2008 11:11:00 +0000

What is Testing?
* An examination of the behavior of a program by executing on sample data sets.
* Testing comprises of set of activities to detect defects in a produced material.
* To unearth & correct defects.
* To detect defects early & to reduce cost of defect fixing.
* To avoid user detecting problems.
* To ensure that product works as users expected it to.

Why Testing?
* To unearth and correct defects.
* To detect defects early and to reduce cost of defect fixing.
* To ensure that product works as user expected it to.
* To avoid user detecting problems.

Testing Techniques

noreply@blogger.com (Unknown) — Mon, 29 Sep 2008 11:10:00 +0000

Black Box Testing -Testing of a function without knowing internal structure of the program.
White Box Testing -Testing of a function with knowing internal structure of the program.

Regression Testing -To ensure that the code changes have not had an adverse affect to the other modules or on existing functions.

Functional Testing:
* Study SRS
* Identify Unit Functions
* For each unit function
- Take each input function
- Identify Equivalence class
- Form Test cases
- Form Test cases for boundary values
- From Test cases for Error Guessing
* Form Unit function v/s Test cases, Cross Reference Matrix
* Find the coverage

Types of Testing

noreply@blogger.com (Unknown) — Mon, 29 Sep 2008 11:08:00 +0000

Unit Testing:
* The most 'micro' scale of testing to test particular functions or code modules. Typically done by the programmer and not by testers .
* Unit - smallest testable piece of software.
* A unit can be compiled/ assembled/ linked/ loaded; and put under a test harness.
* Unit testing done to show that the unit does not satisfy the functional specification and/ or its implemented structure does not match the intended design structure.

Integration Testing:
* Integration is a systematic approach to build the complete software structure specified in the design from unit-tested modules. There are two ways integration performed. It is called Pre-test and Pro-test.
* Pre-test: the testing performed in Module development area is called Pre-test. The Pre-test is required only if the development is done in module development area.

Alpha testing:
* Testing of an application when development is nearing completion minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

Beta testing:
* Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers.

System Testing:
* A system is the big component.
* System testing is aimed at revealing bugs that cannot be attributed to a component as such, to inconsistencies between components or planned interactions between components.
* Concern: issues, behaviors that can only be exposed by testing the entire integrated system (e.g., performance, security, recovery).

Volume Testing:
* The purpose of Volume Testing is to find weaknesses in the system with respect to its handling of large amounts of data during short time periods. For example, this kind of testing ensures that the system will process data across physical and logical boundaries such as across servers and across disk partitions on one server.

Stress testing:
* This refers to testing system functionality while the system is under unusually heavy or peak load; it's similar to the validation testing mentioned previously but is carried out in a "high-stress" environment. This requires that you make some predictions about expected load levels of your Web site.

Usability testing:
* Usability means that systems are easy and fast to learn, efficient to use, easy to remember, cause no operating errors and offer a high degree of satisfaction for the user. Usability means bringing the usage perspective into focus, the side towards the user.

Security testing:
* If your site requires firewalls, encryption, user authentication, financial transactions, or access to databases with sensitive data, you may need to test these and also test your site's overall protection against unauthorized internal or external access.

Capability Maturity Model

noreply@blogger.com (Unknown) — Thu, 28 Aug 2008 07:13:00 +0000

Capability Maturity Model, as already mentioned, is the outcome of decades of research and study of successful and unsuccessful projects. The major philosophy of CMM is very similar to life itself. When a child is born it is at a very "initial" level of maturity. The child grows up, learns and attains a higher level of maturity. This keeps on going until he/she becomes a fully mature adult; and even after that the learning goes on.

According to CMM, a software company also goes (or should go) through similar maturity evolutions. The CMM maturity levels are discussed later.

Readers should notice that CMM is NOT a software development life cycle model. Instead it is a strategy for improving the software process irrespective of the actual life-cycle model used [Schach 1996].

Lets dive right into the intricacies of CMM.

Software project Steps

noreply@blogger.com (Unknown) — Thu, 28 Aug 2008 07:12:00 +0000

Let us start by considering the normal course of events that follow when a software project is undertaken. We will only outline the steps, without going into the details of each; since our purpose is to highlight the most common events and not there particular details, as they may vary depending on the contract and the nature of the project.

Step-1 – The Requirements:

The client gives a set of Requirements of the product to the contracting company (referred to as "the Company"). The first step is to discuss these requirements with the client. The discussion will focus on removing any ambiguity, conflict, or any other issues related to the product in question. The outcome of this discussion will ideally be a "Well-defined set of functionalities that the product will achieve".

Step-2 – The Planning (cost, time estimates):

The next step is to plan the project. Given the required set of functionalities the million dollar question is "How much time and Dollars will the Company require to complete the project?". Based on these estimates, resources (both human and non-human) will be allocated to the project. Various milestones will be defined, to facilitate project monitoring. Plans will also be made to outsource any part of the project, if deemed necessary.

Step-3 – On with the Project:

Assuming that the plans have been made, team formed, and estimates in place now the Company is ready to start actual work on the project.

Step-4 – How is the Project Doing (continuous monitoring):

Once the project is under way, the project will continuously monitor their progress against the Plans and milestones made in Step-2.

Step-5 – How are the sub-contractors Doing:

In Step-2, if the Company decided to outsource or sub-contract a part of the project, then the sub-contractors will also be managed and their progress monitored closely. This will ensure that no delays occur due to lapses caused by the sub-contractor.

Step-6 Software Quality Assurance:

In Step-4 the Company monitored the project for any cost overrun, or any schedule slippage; but that's not all that need to be monitored. An in-budget, with-in-time project may still have serious problems. In Step-4 the Company ensured that the project is going according to the schedule, and is with in budget, but is it doing what it is suppose to do?. That is, are all the tasks completed according to the Company's standards and according to, the Requirements agreed in Step-1?. In Step-6, the Company will ensure that no work is done in violation of any standard and any system Requirements.

Step-7 Handling the inevitable changes:

A software project, usually involves different teams working on different aspects of the project, e.g. one team may be coding a module, while another may be working on writing the users manual. Although Teams work on a certain aspect of the project, but the project is eventually going to be delivered as a single product. It's evident that all the teams MUST co-ordinate their work, to produce a well-integrated final product. In Step-2, the plan was well laid, and all the involved personnel were assigned their share of work. But some changes will almost always have to be made. These changes may affect more than one team. Therefore it is necessary for the Company to ensure that all the bits-and-pieces of the project remain well coordinated. The Company must determine if a change made to one piece of the product also necessitate a change to one or more other pieces, and if it does then those changes must be made accordingly. In Software terms this is called "Configuration Management".

One can come up with many other activities that a software company would normally follow. But we would stop here and will focus only on the above-mentioned activities.

It is obvious that the above mentioned activities are performed by almost all the software companies; then what is it that makes a company Microsoft and another company go bellies up ?.

The answer is simple: Not all the companies observe the above steps with the same vigor. These steps are all very simple to understand but extremely difficult to execute effectively.

The purpose of the above discussion was to enable the readers to appreciate the need for a guideline, or a road map that software companies can follow to produce quality software, with in budget and with in time. One such roadmap is called Capability Maturity Model (CMM).

I shall discuss CMM in the easiest way I could. But the readers must realize that CMM is a tricky model to fully understand and is even trickiest to successfully implement.

CMM – an Introduction

noreply@blogger.com (Unknown) — Thu, 28 Aug 2008 07:11:00 +0000

Is CMM just another buzz word or is there something more to it.

Capability Maturity Model (CMM), has found it's way from Carnegie Melon University's (CMU) software engineering Institute (SEI) to major Software developers all over the world. Some consider it as an answer to Software Industry's chaotic problems, and some consider it just another exhaustive framework that requires too much to do and too little to show for it. This article is not intended to be a comprehensive introduction to CMM, the interested readers should read official CMM documentation available from SEI's web site to get a comprehensive discussion of CMM. This article is intended to show that CMM is not a framework that advocates magical and revolutionary new ideas, but it is in fact a tailored compilation of the best practices in Software engineering.

The intention of this article is to introduce CMM as a logical and obvious evolution of the Software Engineering practices. The article does not require any prior knowledge of CMM; however it is assumed that the reader is cognizant of issues involved in Software development.

Before we move any further, we must define one term that is central to almost every industry – Process. This term has also found its rightful place in Software Industry. It was Deming who popularized this term. Japanese have managed a miraculous industrial revolution based on the simple concept of a Process. " Process is a mean by which people, procedures, methods, equipment, and tools are integrated to produce a desired end result" [quoted from CMM for Software, version 2B]. Humphrey in his Book Introduction to the PSP, (1997) defines a process in Software Development context as " Process defines a way to do a project, Projects typically produces a product, and Product is something you produce for a co-worker, an employer, or a customer.".

Now that we know what Process means, how can we use this knowledge to achieve success. The answer lies in the following three-step strategy:

1- Analyze the current process by which your organization executes its projects,

2- Figure out the strengths and weaknesses of the current process,

3- Improve upon your Process's strengths and remove its weaknesses.

Bingo you have a simple recipe for success !

The above seemingly simple steps, have baffled the Software Industry for years. Different software developers have adopted different techniques to implement the three-step recipe, with varying degree of success.

Having noted down the above "three-step approach to success", we would now concentrate on mastering each of the above three steps.

When and Why to use Descriptive programming?

noreply@blogger.com (Unknown) — Mon, 18 Aug 2008 11:37:00 +0000

Below are some of the situations when Descriptive Programming can be considered useful:
1. The objects in the application are dynamic in nature and need special handling to identify the object. The best example would be of clicking a link which changes according to the user of the application, Ex. "Logout <>".

2. When object repository is getting huge due to the no. of objects being added. If the size of Object repository increases too much then it decreases the performance of QTP while recognizing a object.

3. When you don't want to use object repository at all. Well the first question would be why not Object repository? Consider the following scenario which would help understand why not Object repository

Scenario 1: Suppose we have a web application that has not been developed yet.Now QTP for recording the script and adding the objects to repository needs the application to be up, that would mean waiting for the application to be deployed before we can start of with making QTP scripts. But if we know the descriptions of the objects that will be created then we can still start off with the script writing for testing

Scenario 2: Suppose an application has 3 navigation buttons on each and every page. Let the buttons be "Cancel", "Back" and "Next". Now recording action on these buttons would add 3 objects per page in the repository. For a 10 page flow this would mean 30 objects which could have been represented just by using 3 objects. So instead of adding these 30 objects to the repository we can just write 3 descriptions for the object and use it on any page.

4. Modification to a test case is needed but the Object repository for the same is Read only or in shared mode i.e. changes may affect other scripts as well.

5. When you want to take action on similar type of object i.e. suppose we have 20 textboxes on the page and there names are in the form txt_1, txt_2, txt_3 and so on. Now adding all 20 the Object repository would not be a good programming approach.

Validation

noreply@blogger.com (Unknown) — Fri, 08 Aug 2008 08:32:00 +0000

Determination of the correctness of the final program or software produced from a development project with respect to the user needs and requirements.

Verification

noreply@blogger.com (Unknown) — Fri, 08 Aug 2008 08:31:00 +0000

1. The process of determining whether the products of a given phase of the software development cycle fulfill the requirements established during the previous phase.
2. The act of reviewing, inspecting, testing, checking, auditing, or otherwise establishing and documenting whether items, processes, services, or documents conform to specified requirements.

Walkthroughs

noreply@blogger.com (Unknown) — Fri, 08 Aug 2008 08:31:00 +0000

During a walkthrough, the producer of a product "walks through" or paraphrases the products content, while a team of other individuals follow along. The team's job is to ask questions and raise issues about the product that may lead to defect identification.

White-box Testing

noreply@blogger.com (Unknown) — Fri, 08 Aug 2008 08:30:00 +0000

White-box Testing

A testing technique that assumes that the path of the logic in a program unit or component is known. White-box testing usually consists of testing paths, branch by branch, to produce predictable results. This technique is usually used during tests executed by the development team, such as Unit or Component testing.

Variables- Variable Declaration

noreply@blogger.com (Unknown) — Fri, 08 Aug 2008 08:28:00 +0000

Variables
A variable is a placeholder that refers to a memory location that stores program information that may change at run time. A variable is referred to by its name for accessing the value stored or to modify its value.

Variable Declaration
Variables in VBScript can be declared in three ways:

Dim Statement
Public Statement
Private Statement
For example:
Dim No_Passenger

Multiple variables can be declared by separating each variable name with a comma. For example:
Dim Top, Left, Bottom, Right

You can also declare a variable implicitly by simply using its name in your script. That is not generally a good practice because you could misspell the variable name in one or more places, causing unexpected results when your script is run. For that reason, the Option Explicit statement is available to require explicit declaration of all variables. The Option Explicit
statement should be the first statement in your script.

Note:

Variables declared with Dim at the script level are available to all procedures within the script. At the procedure level, variables are available only within the procedure.

What is VBScript? Data types

noreply@blogger.com (Unknown) — Fri, 08 Aug 2008 08:27:00 +0000

What is VBScript?

VBScript is a subset of Visual Basic 4.0 language. It was developed by Microsoft to provide more processing power to Web pages. VBScript can be used to write both server side and client side scripting. (If you already know Visual Basic or Visual Basic for Applications (VBA), VBScript will be very familiar. Even if you do not know Visual Basic, once you learn VBScript, you are on your way to programming with the whole family of Visual Basic languages.)

Data types

VBScript supports only one data type called 'Variant'. The variant data type is a special kind of data type that can contain different kinds of information. It is the default data type returned by all functions in VBScript. A variant behaves as a number when it is used in a numeric context and as a string when used in a string context. It is possible to make numbers behave as strings by enclosing them within quotes.

QTP Question 02: What's New in Quick Test Professional 8.2?

noreply@blogger.com (Unknown) — Tue, 05 Aug 2008 06:20:00 +0000

Keyword View: Lets you easily build and maintain tests without writing VBScripts.
Auto-Documentation: Provides improved test clarity and the ability to view test steps in plain English.
Step Generator: Allows you to quickly insert custom-built functions into your tests.
Mercury Business Process Testing: Enhanced integration with BPT -- Business Components, Scripted Components, and Application Areas.
Enhanced Expert View: Provides greater efficiency when generalizing test components.
Action Parameters: Allows you to generalize testing actions for greater reusability.
Data Parameters: You can now specify test or action parameters to pass values into and from your test, and between actions in your test.
Open XML Report Format for Test Results: Test results are now stored in an open XML format, enabling you to easily customize the reports according to your own requirements, and to integrate the test result information with other applications.
Unicode Support: Lets you test global deployments of your enterprise applications.
Function Definition Generator: You can use the new Function Definition Generator to generate definitions for user-defined functions, add header information to them, and register functions to a test object.

QTP Question 01: What is QTPro? What is Quick Test Pro? What is Quick Test Professional?

noreply@blogger.com (Unknown) — Tue, 05 Aug 2008 06:20:00 +0000

Mercury Quick Test Professional™ provides the industry's best solution for functional test and regression test automation - addressing every major software application and environment. This next-generation automated testing solution deploys the concept of Keyword-driven testing to radically simplify test creation and maintenance. Unique to Quick Test Professional's Keyword-driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. QuickTest Professional satisfies the needs of both technical and non-technical users. It enables you to deploy higher-quality applications faster, cheaper, and with less risk. It works hand-in-hand with Mercury Business Process Testing™ to bring non-technical subject matter experts into the quality process in a meaningful way. Plus, it empowers the entire testing team to create sophisticated test suites with minimal training. The deployment of Mercury Quick Test Professional is optimized through the use of Mercury best practices. Mercury best practices cover all aspects of deployment, including product installation and operation, organizational design, process implementation, continual process improvement and measurement of return on investment (ROI). Throughout your implementation Mercury applies these best practices to your specific situation, creating world-class procedures for you that drive long-term success.source

Creating Output Values

noreply@blogger.com (Unknown) — Mon, 04 Aug 2008 07:02:00 +0000

In Parameterizing Tests, you created parameters that inserted different data into each iteration of a test run. You can also retrieve data from your application and output it to the Data Table, using output values. This data can then be used at a later stage in the test. QuickTest displays the retrieved data, following the test run, in the Runtime Data Table.

For example, you can use an output value to verify that the date or flight number is correctly displayed in two different Web pages, by using the value obtained in one page as the expected text that QuickTest checks for in the other page.

In this lesson you will learn about:

Creating an Output Value
Running and Analyzing a Test with Output Values

Creating an Output Value

noreply@blogger.com (Unknown) — Mon, 04 Aug 2008 07:01:00 +0000

In Parameterzing Tests, the second and third iterations of your test failed because the ticket price changed when the departure city changed. The checkpoint that checked the fare of the outbound flight in the Book a Flight: Mercury page did not update its expected value as the fare changed.

In this lesson, you will create an output value that retrieves the outbound fare from the Select a Flight: Mercury page in each test iteration. You will then modify the table checkpoint you created, so that it checks that the price displayed in the Book a Flight: Mercury page matches the price captured in the Select a Flight: Mercury page.

· Start QuickTest and open the Parameter test.

If QuickTest is not already open, choose Start > Programs > QuickTest Professional > QuickTest Professional.

o If the Welcome window opens, click Open Existing.

o If QuickTest opens without displaying the Welcome window, choose
File > Open or click the Open button .

In the Open Test dialog box, locate and select the Parameter test, then click Open.

· Save the test as Output.

Choose File > Save As. Save the test as Output.

· Confirm that the Active Screen option is enabled.

If you do not see the Active Screen at the bottom of the QuickTest window, click the Active Screen button or choose View > Active Screen.

· Select the text you want to use as an output value.

In the Keyword View, expand Welcome: Mercury Tours and click the Select a Flight: Mercury page. The page is displayed in the Active Screen.

In the Active Screen, highlight the fare, without the $ sign, for the outbound flight (New York to San Francisco)—270.

Right-click the highlighted text and select Insert Text Output. The Text Output Value Properties dialog box opens.

· Rename the output value.

In the Name box, enter PriceOutput as the new output value name.

· Set the output value settings.

Click the Modify button to open the Output Options dialog box.

The Name box displays Select_a_Flight_MercuryOutput_Text_out. Delete this and enter depart_flight_price.

Click OK to accept the other default settings and close the Output Options dialog box. Click OK again to close the Text Output Value Properties dialog box. QuickTest adds the depart_flight_price column to the Data Table.

QuickTest adds the output value operation to the Select a Flight: Mercury page in the Keyword View.

· Modify the table checkpoint that checks the ticket price displayed in the flight Summary table.

In the Keyword View, expand Welcome:Mercury Tours > Book a Flight: Mercury.

Right-click Checkpoint ("CheckCost") in the Value column, and select Checkpoint Properties. The Table Checkpoint Properties dialog box opens.

Click column 3 in row 3 (the checked cell). In the Expected Data tab, select Parameter and click the Parameter Options button . The Parameter Options dialog box opens.

In the Name box, select depart_flight_price.

Click OK to close the Parameter Options dialog box.

The Table Checkpoint Properties dialog box is redisplayed, with a parameterization icon next to the table value you parameterized.

Click OK to close the Table Checkpoint Properties dialog box. The checkpoint is now parameterized.

· Save the test.

Choose File > Save or click the Save button.

Running and Analyzing a Test with Output Values

noreply@blogger.com (Unknown) — Mon, 04 Aug 2008 06:59:00 +0000

You will now run the test and examine the results.

Run the Output test.
Click the Run button or choose Automation > Run. The Run dialog box opens.
Select New run results folder and accept the default results folder name.
Click OK. When the test run is completed, the Test Results window opens.
1. Examine the run-time data results.
In the Test Results window, select Run-Time Data Table from the results tree. The output values used during the test run are displayed in a grid. Note that a different price is shown in the depart_flight_price column for each iteration.
Examine the checkpoint results.
Choose View > Expand All.
In Output Iteration 1 (Row 1), under the Book a Flight: Mercury page, click Checkpoint "CheckCost".
Note that in the Details pane, the checkpoint is marked in green as passed because the price of the ticket for the first flight in the Summary table matched the expected value obtained from the Select a Flight page.
Examine the checkpoints for Iterations 2 and 3 as well. In the Details pane, these checkpoints are also marked in green as passed, for the same reason.
Close the Test Results window.

Choose File > Exit to close the Test Results window.

Enhancements in QTP 9.5

noreply@blogger.com (Unknown) — Fri, 01 Aug 2008 11:14:00 +0000

HP has made some major enhancements in QTP 9.5 over the previous versions. [For earlier versions, Please refer difference between QTP 8.2 and 9.2]

Environment Support:

QTP 9.5 supports MS Vista 64 bit edition also, in comparison to QTP 9.2's support for 32 bit edition only.
Support for omnipresent tabbed browsing is also introduced with this version.

Installation and Add-ins:

QTP 9.5 offers all add-ins integrated with the core installation package. Though you still need to buy add-ins separately to get them activated.
For installing QTP 9.5 you have to do a clean uninstall (as mentioned in the HP KB) of previous versions. That means, now on, you would not be able to upgrade from the previous versions.

QTP IDE:

A refreshing enhancement in QTP IDE GUI I liked this time was the introduction of the ability to see functions related to current tests. Whether you have an external file containing functions or they are inside a reusable actions, you would be able to see all of them at one place. Now no need to dig and scroll through the endless list of functions in your notepad!

Bitmap checkpoint: Earlier using bitmap checkpoint was a pain in a sense that a minor change in pixel and your test would fail. To increase the tolerance we have to go inside windows registry and change the required tolerance value. With QTP 9.5 HP has introduced support for tolerance level direct from the GUI. You can define tolerance in terms of RGB and/or pixels.

Web Add-in Extensibility: Using this feature you can configure and extend the support to those 3rd party custom web controls ( and new technologies like AJAX) which were not supported with the earlier versions. You need to possess fair amount of JavaScript knowledge to handle this. How much help this feature really provide is yet to be seen!

Download 14days QTP 9.5 evaluation

Please let me know your views on this new version of QTP in the comments section below.

How to write test cases for web applications using QTP

noreply@blogger.com (Unknown) — Fri, 01 Aug 2008 07:31:00 +0000

Answer: Browser("micClass:=Browser").Page("micClass:=Page").WebEdit
("name:=property").action

This is a sample of how you can write a a test script for a
web application.

6. What is keyword view and Expert view in QTP?

noreply@blogger.com (Unknown) — Mon, 28 Jul 2008 09:19:00 +0000

- Quick Test's Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View

4. How to use the Object spy in QTP 8.0 version?

noreply@blogger.com (Unknown) — Mon, 28 Jul 2008 09:18:00 +0000

- There are two ways to Spy the objects in QTP: 1) Thru file toolbar, In the File Toolbar click on the last toolbar button (an icon showing a person with hat). 2) True Object repository Dialog, In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and release the Ctrl button.

3. What is the use of Text output value in QTP?

noreply@blogger.com (Unknown) — Mon, 28 Jul 2008 09:17:00 +0000

- Output values enable to view the values that the application talks during run time. When parameterized, the values change for each iteration. Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.

2. How to handle the exceptions using recovery scenario manager in QTP?

noreply@blogger.com (Unknown) — Mon, 28 Jul 2008 09:17:00 +0000

- There are 4 trigger events during which a recovery scenario should be activated. A pop up window appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions.You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has three steps: 1. Triggered Events 2. Recovery steps 3. Post Recovery Test-Run

1. What are the Features & Benefits of Quick Test Pro (QTP 8.0)?

noreply@blogger.com (Unknown) — Mon, 28 Jul 2008 09:16:00 +0000

- Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving capability. Identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a single step with Auto-documentation technology. Enables thorough validation of applications through a full complement of checkpoints.