QTP/UFT

2017-04-21T04:14:00.000-07:00

XML is a markup language designed to store data in a format that can be both readable by human and machine. Using XML, data can also be easily exchanged between computer and database systems.

Sample XML and their key elements are represented below −

Accessing XML

Const XMLDataFile = "C:\TestData.xml"

Set xmlDoc = CreateObject("Microsoft.XMLDOM")

xmlDoc.Async = False

xmlDoc.Load(XMLDataFile)

' Getting the number of Nodes (books)

Set nodes = xmlDoc.SelectNodes("/bookstore/book")

Print "Total books: " & nodes.Length ' Displays 2

' get all titles

Set nodes = xmlDoc.SelectNodes("/Booklib/book/value/text()")

' get their values

For i = 0 To (nodes.Length - 1)

Title = nodes(i).NodeValue

Print "Title is" & (i + 1) & ": " & Title

We can compare two given XMLs −

Dim xmlDoc1

Dim xmlDoc2

' Load the XML Files

Set xmlDoc1 = XMLUtil.CreateXMLFromFile ("C:\File1.xml")

Set xmlDoc2 = XMLUtil.CreateXMLFromFile ("C:\File2.xml")

'Use the compare method of the XML to check if they are equivalent

Comp = xmlDoc1.Compare (xmlDoc1, xmlDoc2)

'Returns 1 if the two files are the same

If Comp = 1 Then

Msgbox "XML Files are the Same"

Else

Msgbox "XML Files are Different"

End if

Transaction point in QTP

2016-12-27T00:43:00.000-08:00

Transaction point:

It is a concept introduced in QTP which is used for calculating the time taken by an application to perform a specific task or the execution time of a block of statement.

QTP has provided the following transaction options.

Start transaction
End transaction

Syntax:

Services.start transaction ”transaction name”

“ statement 1”

“ statement 2

Services.end transaction ”transaction name”

QTP Framework:

2016-12-27T00:42:00.000-08:00

Hi Friends while I was exploring different blogs or different community or networking websites i found mainly many questions related to QTP framework.Here i am going to share a article with you that how we can establish a QTP framework and what are the main things need to take care while creating a framework.

1. The automation process
The following sections describe in detail the process required to create automated scripts to regression test existing projects with maintenance releases.

1.1. Automation Workflow
The diagram above depicts the process in which existing applications require automation for regression testing.

1.1.1. Pre-requisites for QTP Automation Process
The following are pre-requisites or dependencies for QTP automation:
• Knowledge and hands-on experience with the use of QTP;
• Quality Centre (QC) and QTP installed and configured;
• QC and QTP are integrated;
• QTP Add-Ins are installed (if required);
• QC user groups are defined and granted access to Quality Centre projects;
• The application or product is in a stable state;
• Creation of new automated scripts requires existing manual test cases to have been executed successfully. This task is performed by the application tester or business representative and is performed prior to handover to QTP automation.
• The manual test cases must have been executed successfully and that there are no other changes in the application. Existing automated scripts can be updated directly to reflect the changes as part of maintenance releases.
• All test cases must start and end at the same point. This is normally the First screen of the application. This allows for test cases to be batched together into a test suite.
• All environment, software or data table changes must be advised to the automated testing team. There will potentially be an impact on the running of automated test cases with the introduction of these changes.
• The test cases must not be data dependant. All data required in the test case must be created in the test case. In the event that data cannot be created and the test case is data dependant, the data must be able to be restored, or manipulated back to the initial state after a test case updates the data. This then allows for any test case to be rerun at anytime

Existing manual test cases exist in QC in the standard format (see the QC user guide) and a copy of the test case to be automated are placed in the regression folder alongside any existing automated scripts.

2. QTP Functional Testing Methodology
Each Test case is built using a series of Quick Test Professional Functions. Each function executes Quick Test Professional code to input data onto a screen.
Each object in the Quick Test Professional Function resides in the Object Repository, thus allowing Quick Test Professional to identify all fields in the application.
• Each test case uses functions. Each function is either an applet on a screen or a whole screen depending on the amount of fields.
• Each function is named AUT_Screen Name e.g. MRS_Close_Application
• Every field/object on the screen or applet must be learnt into the object repository and renamed where required to a more meaningful screen name.
• Each function library must reside as .vbs file
• All functions are accessible via the step generator.

Function is placed into testcase via the step generator. The rc value is passed back to Quality Centre via the Reporter. ReportEvent rc command. Quality Centre accepts 0 for a pass, 1 for a fail and 2 as done. Always try to pass 1 or 0.

The testcase function call invokes the function as displayed above. This is the actual vbscipt that drives QTP. Each function uses a function template. Define in the function, the variables to uniquely identify the screen and any fields on the screen.

The function displayed above selects links via a parameter link_name. The links have been learnt into the object repository. Notice the browser, page and frame name are the same as what has been learnt into the object repository.
2.1. Initial Condition
Automated test scripts must begin from the same starting point. It is best practise to end all open browsers and start the Application under Test from the beginning. This ensures that all scripts can run back to back in an unattended batch mode.

2.2. Start Up Script
The start up script will copy all functions from the LAN and load them on the C Drive of the PC executing the test case. It will also build the infrastructure libraries if they don’t exist.
2.3. Test case Failure / Exception condition handling

All Quick Test Professional functions must use an exception handling framework. This allows any Quick Test Professional function to fail, report the failure and backout of the application.
The exception handling framework is built by:
An Environment Variable set in the Quick Test Professional startup_script set as ENVIRONMENT(EXCEPTION_COND)=”N”.

The MRS_Logon function sets the ENVIRONMENT(EXCEPTION_COND) to a value of “N”.
If any function has a failure by not finding the screen is should be on, or any known exception condition is triggered, the EXCEPTION_COND value is set to “Y”. The application is shutdown and all functions in that testcase flush. The next use of a MRS_Logon function will reset the EXCEPTION_COND to “N”.

The following diagram demonstrates the exception handling process:

3. Create Infrastructure
Infrastructure libraries are created to store QTP functions, utilities, documentation and object repository files
The Infrastructure libraries are created for each release of the software. Under each release folder (eg REL23) the folders below must exist, otherwise QTP will fail in the startup script.
Examples of the libraries for releases are as follows:
\\HCOPROD4\QSA\Group\QTP_MRS\REL23\Documentation
\\HCOPROD4\QSA\Group\QTP_MRS\REL23\Functions
\\HCOPROD4\QSA\Group\QTP_MRS\REL23\Repository
\\HCOPROD4\QSA\Group\QTP_MRS\REL23\Testcase
\\HCOPROD4\QSA\Group\QTP_MRS\REL23\Txtfiles
\\HCOPROD4\QSA\Group\QTP_MRS\REL23\Utilities

The following diagram displays the directory structure for the Rel23 libraries. They are as follows

:
3.1. Library Definitions for each Release
The application under test must have a QTP release specific directory, i.e. REL11, REL 12 and Sandpit
Each of the release directories hold release specific infrastructure code or release specific infrastructure objects that QTP requires in order to run the application under test. Therefore the REL11 functions folder will hold all functions that execute on the Rel11 application code and the REL12 functions folder will hold any new application screen functions and modified Rel11 functions.

3.2. Sandpit Libraries
Sandpit libraries are for use on the test automator’s pc to develop or modify QTP code. By saving in these libraries, data is not overwritten with the baseline code after a restart of QTP.
The sandpit libraries remain empty on the \\HCOPROD4\QSA drive. The sandpit library on the C drive is where changes can be made or new functions can be created. Once tested, they can be appended to the end of the Function or Utility VBS files on the \\HCOPROD4\QSA drive under the appropriate Release Folder.
The function and utility Sandpit libraries must contain a template function. If not, these libraries cannot be executed via an executefile command.

3.3. Documentation
The Documentation directory holds Word or Excel documents which reference the application.

4. Functions Library
The Functions Library contains QTP functions. These are based on one function per screen. This library is a sequential file of all the QTP functions for that application release. As more than one software release can be tested at any one time, the QTP function library can be concatenated in QTP with as many prior function libraries as required. The following shows a library concatenation of rel13, rel12 and rel11
Sandpit
FunctionABC
FunctionDEF
REL12
Function XYZ
REL11
Function 123
Function 346
FunctionABC

The above shows that Sandpit function FunctionABC would be a modified version of REL11 Function ABC and a new function functionDEF as the sandpit library would override the rel11 function library.
As each application release gets tested, only the new functions and functions that require modification are held in the Sandpit function library. All Functions that are not changed are still accessed via the concatenation of new and old release function libraries in the QTP Startup
The QTP startup script will copy all available Release folders to the C:Drive or D:Drive of each test machine.
At the end of each VBS file, an ENVIRONMENT library variable will be used to load other libraries if required.

4.1. Function Creation
When creating a new function, the following steps must be followed:
1. Learn Object Repository entries into the \\HCOPROD4\QSA drive Object Repository.
2. Rename Object Repository entries to meaningful names.
3. Create function by copying the template function into your sandpit/function library
4. Add the field names of the screen to the parameter list of the function.
5. Add the new Object Repository entry names into the function, as AP_webedit, AP_weblist, etc. This will allow the function to communicate to the object repository and play data into each field
6. Save the function and test change
7. Once satisfied that new function is ok, append it to the \\hcoprod4\qsa drive function library.

4.2. Object Repository
The Object Repository library holds all the application objects for the application under test. This library is not concatenated as only one Object Repository, with the same entries in it, can be opened at any time.
When creating a new release of the Object Repository, a “save as” must be done on the old Object Repository to the new release library. Any subsequent changes can then be done in the new Object Repository library.
When a QTP script is executed, a copy of the Object Repository is taken and saved to C:\Application\Release\Repository. This is done to ensure no corruption occurs on the master that is held on the \\HCOPROD4\QSA drive.
If changes are required, they must be done directly to the \\HCOPROD4\QSA drive copy of the object repository. This is because when merging two object repositories, QTP sees like defined objects as the same.
By learning new objects into the \\HCOPROD4\QSA drive Object Repository a rename on objects can be done and the Object Repository can be resaved onto the \\HCOPROD4\QSA drive. Ensure that a backup of the object repository is done first. If the Object Repository gets corrupted, then QTP will not run.
E.g. MRS uses \\HCOPROD4\QSA\Group\QTP_MRS\REL23\Repository\MRS.tsr .The Object Repository is copied from the \\HCOPROD4\QSA:\Group\QTP_MRS\REL23\Repository\MRS.tsr folder when the test case starts to C:\Group\QTP_MRS\REL23\Repository\MRS.tsr.

4.2.1. Object Repository Naming Standards
Any object placed into the Object Repository should be named according to the field name on a screen. As web GUI entries will be captured as the html programming name, rename this to an understandable name such as CustomerName or CustomerPhoneNumber. This will then mean the GUI entry is shown in functions and test scripts as something understandable. A GUI entry in the format F032fwfn is not acceptable.
Any GUI entries that are non web based must also have an understandable name.

4.3. Testcase Folder
This library holds reusable actions that we can use for data loading. i.e. creating a piece of data that we can reuse in the test script later. Any data that is created must be saved as an Environment variable.
This library also contains the startup script and template script.
4.4. Txtfiles Folder
This library holds files that are created at run time. This can also be used for transient data that is used between test scripts. This practice is not recommended as test cases should be data independant.
4.5. Utilities Folder
This library holds non specific functions that can be used in any test script. Functions may include reading and writing from files, button press, edit sets, list selects etc.

5. Build Automated Scripts
5.1. Manual Test Cases
Each Test Case must be written into Quality Centre. From Quality Centre, login to your project and select the test case. The Details tab of Quality Centre describes the tests Purpose, Test Conditions, Pre requisites, Dependencies, Environments and post-test Cleanups.
View your ‘manual’ steps by clicking on the tab, Design Steps. Ensure that manual Test Cases have been written and executed without error and are therefore verified as correct before automating.

Before any test case is automated it must pass the following criteria:

• Each script has been written so that each application screen in the test case flow is a new test step and each verification point is a new step.
• Test cases are stand alone, non data dependant, logon to the application under test at the start and logoff or shutdown the application at the end of each test case.
• All data requirements are defined in the details tab of Quality Centre.

5.2. Generate QTP Script
You can now convert this manual Test Case in to a Quick Test Professional script. To do this, click on the Generate Script button and select the QUICKTEST_TEST option.

Quality Centre has now generated Quick Test Professional code and has attached it to this manual Test Case. This can be viewed by clicking on the tab Test Script. This generated code is nothing more than a series of comments and reporter events. The Quality Centre manual Test Case has been copied in to Quick Test Professional and each step has been placed in as comments.

5.3. Generated QTP Script
After generating a Quick Test Professional script from Quality Centre all the Step details are placed into comments in the Quick Test Professional script

5.4. Test Settings and Options
Each new script requires test settings, record and run settings, associate repositories and options to be set.
5.4.1. Test Settings
Click on File and select Settings. Click on Run tab. Ensure that ‘Run on all rows’ is selected. At field: When error occurs during run session: select ‘proceed to next step’.
Ensure that the two tick boxes are also ticked.

Click on Resources tab. Click on ‘+’ to add resource library and utilities. Ensure that functions are associated to local C:\ or D:\ and that sandpit libraries are listed first.

5.4.2. Record and Run Settings
Select Automation, then Record and Run Settings.
When using a Windows based application, set as per example below:

5.4.3. Associate Repositories
In QTP, click on Resources and then select Associate Repositories. Click on ‘+’ to create repository association. Click on ‘>’ to associate ‘Action1’.

5.4.4. Options
Click on Tools, select Options. Click on Run tab. Ensure Run Mode is set to ‘Normal’. As displayed in diagram above, ensure the following are ticked:
- View results when run session ends
- Allow other Mercury products to run tests and components
- Save still image captures to results. Select ‘For errors’ from drop list

5.5. Step Generator
All Quick Test Professional functions are written and stored in Libraries and are added to the Step Generator (F7) in Quick Test Professional.
To access these functions, click on Insert, then Select Step Generator or press F7 from within QTP.
The functions have been sorted alphabetically to make it easier to find the function that matches your Application screen. Once you have found the function that will perform the functionality matching the Application screen, you can fill in the value column with appropriate arguments that will be set to the function.
Every parameter must have an argument value specified. The return value box needs to be ticked each time a new function call is set. Insert another step to be ticked as required.
When creating a function you must enter data into every field of the function to verify it can run the function correctly.

The return value (rc = return code) stores whether the function has passed or failed. The rc is then passed to the report and decides whether the particular step has passed or failed.

5.6. Editing QTP Scripts
Now edit and build the Automated Test Script via Quick Test Professional. To make the script workable, we begin adding in to the Test Script the functions or Test conditions that will perform the automated tests, thus building up a test scenario. The idea here is to match the manual Test Case steps to the appropriate Quick Test Professional Function.

Each test case should have one or more Quick Test Professional functions per step. This function will relate to each screen of the tested application, as per the Automated Functional Testing Methodology.

The Automated Functional Testing Methodology gives the advantage of modular programming; it enables an easy and fast way to create reusable test cases. Other advantages of this methodology are, ease of maintenance of scripts and ability to run scripts in any environment due to no data dependencies.

Ensure that you add the following text at the top of the Quick Test Professional script to identify who has written the script and when:

E.g. “# Revision History: KH Initial Version 10/03/08 MRS version 2.2.3”

You are now ready to edit/create the Automated Test Script. To do this, start up Quick Test Professional and access the test script that was created in Quality Centre via the Open command. There are two areas where Test Scripts can reside. They can reside within Quality Centre or in the File System (PC or Network folders).

If we have created the Test Script via Quality Centre then the script will reside with in Quality Centre. Just follow the same path you used when accessing the Manual Test Script, to find the Automated Test Script.

5.7. QTP Add-Ins
When Quick Test Professional scripts are created from Quality Centre, Quality Centre sets the script default addin setting to blank.

Once you have started up the Quick Test Professional script you have to add all the Add-ins for the application under test. To do this, go to File / Test Properties… and click on the Add-ins tab. From here you can select all the add-ins that will be needed by clicking on appropriate items then pressing Enter.
If this is not done, Quick Test Professional will be forced to shutdown and the script will not run at all, due to Webtest commands being executed in the functions while the WebTest addins have not been started when Quick Test Professional is invoked.

Alternatively, any add-ins can be selected during opening QTP application.

5.8. QTP Template Script
Each test case will use a template script at the start. This script will copy all functions from the LAN and load them on the C Drive of the PC executing the test case. It will also build the infrastructure libraries if they don’t exist.
It will then execute a function.vbs file so at run time these functions will override the function library associated at build time.
The template script will be administered by QSA.
The location of the template is:
\\hcoprod4\Group\ QTP_MRS\REL23\Testcase\ActionTemplate.mst
The PC that will be running the automated scripts will reference the abovementioned Action template. A copy of this template is placed in C:\Program Files\Mercury Interactive\QuickTest Professional\dat

5.9. Completed Testcase
Each test case should have one or more QTP functions per step. The function should pass a return code back to the test case, therefore allowing QTP to pass Quality Centre the step status.
At the start of each test case, pre required data can be added. Most pre required data for MRS can be created using a test case that uses variables, e.g. first name and surname. A global variable is created which can be addressed anywhere else in the test case.
Any pre required data scripts exist in QTP_MRS/Rel23/Testcases. These testcases are reusable actions. The line RunAction denotes a called action.
The tester should ensure they have a good understanding of what is available. If new data scripts are required, it is best to model them off existing scripts.
A test case will appear as per the following example:

6. QTP – Connection to Quality Centre
6.1. Connection
Server Connection
From Quick Test Professional, select Tools; Quality Centre Connection and on the Quality Centre Connection page enter the following:
Server url: http://postapps/qcbin Click on button Connect
E.g. Project Connection
Domain: PROJECTQC
Project: MRS
User Name: QC_MRS
Password: Click on button Connect
Other
Reconnect at startup: check this box.
Save password for reconnection on startup: check this box.

7. Maintenance Approach
To ensure that release changes of software can be accommodated by QTP, some tasks must be completed before running any tests.
7.1. Regression Test Changes
When a new release of software causes old functions to perform incorrectly, changes need to be done to these functions and object repositories to allow for testing to continue. These changes may be due to a new screen, a screen change or an object being seen differently in QTP, e.g. a change in a button name.
7.2. New Infrastructure
When building a new release of QTP Infrastructure, the first thing to do is build the infrastructure libraries as documented previously. This will give you the ability to make release dependant changes to old functions, scripts and Object Repositories in the new libraries.
Copy the QC folder within the project to a new version. This will allow for test cases changes in the new version of the QC folder and also keep the old QC folder as is. This will allow for easier reporting of the testing effort in the new release.
7.2.1. Building a new QTP Environment
As each new release of software is placed into an application testing environment, the QTP environment will need to be updated to allow for new functions, and the ability to run regression tests against the old software. The following tasks need to be performed to build the environment:
• The release specific infrastructure libraries must be created for the new release, as documented earlier in Section 4.
• The Object Repository for the current release must be “saved as” into the new release Repository folder
• The Function Library requires just a comment in it, so it does not appear as an empty file.
• The C:\TEMP\QTP_Start_Up.vbs file must be modified with the correct version of the application you wish to test with. Depending on the Release or Project, this is to be updated accordingly.
Once this is completed, restart QTP and ensure you are able to run a script through to completion. Any function changes can then be done by copying the function from the previous release’s function library and placing it into the new function library. From this new function library, you are then able to make the appropriate changes.
The following steps outline the build for new environment:
1. Open Windows explorer.
2. On network \\hcoprod4\qsa, open QTP_MRS folder
3. Create new folder e.g. REL31 and then create folders as per previous release:
- Documentation (to be empty)
- Functions (to contain blank function.vbs file)
- Repository (to contain empty repository file)
- Testcase (Copy Startup and QTP Startup from previous release)
- Txtfiles (to be empty)
- Utilities (to contain blank utilities.vbs)
4. Highlight the Testcase folder.
- Open up QTP Startup.vbs. Update release number in path
- Open up Startup.vbs. Update Dim Release +1 (2) and Add Release (2)
- Add Revision comments. Updates to be made in new function.vbs.

Dictionary Object

2011-10-10T23:42:00.001-07:00

Scripts often retrieve information from an outside source, such as a text file or a Database. After this information has been retrieved, it needs to be stored in Memory so that the script can act upon it. Information such as this can be stored Dictionary object.

The Dictionary object functions stores values in key-item pairs. The Dictionary object is similar to a Collection object .Like an array or a Collection object, Dictionary object holds elements, called items or members, containing data. A Dictionary object can contain any data whatsoever, including objects and other Dictionary objects. Access the value of these dictionary items by using unique keys (or named values) that are stored along with the data. Dictionary is a COM object.

Creating Dictionary

Set oDictionary = CreateObject("Scripting.Dictionary")

Adding Key-Item Pairs to a Dictionary

Set oDictionary = CreateObject("Scripting.Dictionary")

oDictionary.Add "Fax", "Faxing"

Here the Key is Fax and Key Value is Faxing

Descriptive Programming:QTP

2011-10-10T23:20:00.000-07:00

As I described earlier that how QTP identifies test objects during execution.

The answer is simple that during run time it recognize the test object by referring to its object repository ,where we already have stored test object earlier(before creating any test we must make QTP to learn all the test required test object and store it in object repository).

Now the Question is the application is not ready then there is no test object available, then how QTP will learn the test objects and what will we store in the object repository??

Now answer may be the one of the following or all

1) It is impossible to automate any application which is not ready.

2) QTP cannot work without Object repository.

3) What QTP will learn and where will it store.

But all of the above answers are totally wrong J

There is concept/technique which is known as Descriptive Programming is the solution for those.

If we are using object repository then during the run session, QTP finds the object in the object repository based on its name and parent objects, and uses the stored test object description for that test object to identify the object in the application.

We can also instruct QTP to perform operations on objects without referring to the object repository or to the object's name. To do this, we provide QTP with a list of properties and values that QTP can use to identify the object or objects on which we want to perform an operation. This technique is known as Descriptive Programming (inserting programming descriptions).

There are two types of programmatic descriptions:

<!Static. List the set of properties and values that describe the object directly in a VBScript statement

Synatx: Testobj(“Propname1:=PropVal1” , “Propname2:=PropVal2”)

TestObject. The test object class.

PropertyName:=PropertyValue. The identification property and its value.

Each property:=value pair should be separated by commas and quotation marks

Example :

Browser("Title:=Mercury Tours").Page("Title:=Mercury Tours").WebEdit("Name:=Author", "Index:=3").Set "Alok"

2) Dynamic. Add a collection of properties and values to a Description object, and then enter the Description object name in the statement.

The Dynamic type provides more power, efficiency, and flexibility.

We can use the Description object to return a Properties collection object containing a set of Property objects. A Property object consists of a property name and value. We can then specify the returned Properties collection in place of an object name in a statement. (Each property object contains a property name and value pair.)

To create the Properties collection, you enter a Description. Create statement using the following syntax:

Set MyDescription = Description.Create()

Example:

Set Objbtn = Description.Create()

Objbtn(“value”).Value = “Google Search”

Objbtn(“type”).Value = “submit”

Browser(“Google”).Page(“Google”).WebButton(Objbtn).Click

Note: For getting the object properties and their values respectively please refer the Object Spy section described in earlier posts http://expertqtp.blogspot.com/2011/05/object-spy-in-qtp.html

QTP: Recovery scenarios in QTP

2011-10-05T02:18:00.000-07:00

Recovery Scenarios

Unexpected events during a test run disrupt a test or may give invalid test results. For example, during a test run, an application error may occur. This error does not permit the automated test to navigate to the feature, screen, or module that needs to be tested. These unexpected errors and events are called exceptions.

Recovery scenarios are used when you cannot predict at what step the error can occur .

When QTP encounters an exception during a run session, it displays a run error window.

A recovery Scenario consists of the following components:

Trigger: Specifies the exception that may occur during a run session.

The following are the 4 trigger event that QTP provides.

1.Pop up window

2.Object state

3. Test run error

4.Application crash

Recovery: Instructs QTP how to handle the exception

Post-Recovery: Instruct QTP how to proceed after the recovery operations are performed.

The following are the 6 Post-Recovery steps that QTP provides

1) Repeat current step and continue

2) Proceed to next step

3) Process to next action or component iteration

4) Proceed to next test iteration.

5) Restart current test run.

6) Stop the test run.

QTP Interview Questions:QTP

2011-10-04T09:20:00.000-07:00

Hi Friends the few are some questions which are related to QTP interview ,which may be useful.

QTP Interview Questions -1

1) What are the advantages in Test Automation?

a) Fast: Test Tool runs tests significantly faster than human users.

b) Reliable: Automation tool can perform the same operation each time, if we repeated multiple times, so that we can eliminate human errors.

c) Repeatable: We can check how application or website reacts after repeated the same operation with multiple times.

d) Reusable: Automation scripts are reusable on different version of the application of websites even if the user interfaces changes.

e) Comprehensive: In automation testing we can build a suit of tests that covers every feature in the application or website.

f) Programmable: We can program sophisticated Tests that bring out hidden information from the application

2) What are the drawbacks in Test Automation?

a) It is expensive

b) We cannot automate all areas.

c) Lack of Skill

d) It has some limitations (It cannot test every thing)

3) What type of test tools available in the industry?

We can segregate Test tools in 2 categories

a) Business Classification

1) Vendor Tools

2) Open Source Tools

3) In-house Tools

b) Technical Classification

1) Functional and Regression Test Tools

2) Load/Stress/Performance Test Tools

3) Security Test Tools

5) Test Management Tools

6) Unit Test Tools

7) Requirement Management Tools Etc...

4) What are the important factors in test tool selection?

a. Technical factors:

i. Nature of the AUT (Application Under Test)

ii. Tool Features (Facilities available)

iii. Availability of Skilled professionals

iv. Organizations experience

v. Technical support from vendor

b. Business factors:

i. Budget

ii. Vendor’s Reputation

iii. Client’s Interest

5) What test cases can be automated?

Test cases that we want to execute on number of versions of the software

Ex: Regression test cases

Test cases that we want to execute with multiple sets of data

Ex: Data driven test cases

Test cases having complex functionality

6) What test cases cannot be automated?

o Dynamically changing functionality

o Test cases that require more Human interaction

o CUI (command user interface) based test cases

7) Explain about the Testing process in QTP?

Planning:

o Analyzing the Application

o Automation Framework Implementation

o Selecting/Generating Test cases for Automation

o Collecting Test Data

o Configuring Tool Settings

Generating the basic tests

Using Object Repository method or using Descriptive Programming, we can generate Tests

Enhancing Tests

With respect to our project requirements, we have to enhance our tests. For enhancing tests QTP is providing various features like:

o Inserting Transaction points

o Synchronization

o Parameterization

o Inserting VB script Flow Control statements

o Adding comments

o Calling Functions/ calling Actions

o Using Environment variables

o Entering Regular Expressions

o Inserting Checkpoints

o Inserting Output values

Etc..

Note: For any Test all enhancement methods not required.

Debugging Tests (if required)

It is optional; basically scripting languages are Light weight languages, no need to compile them separately. During execution Scripts can be compiled and Run.

If we have any doubts about some scripts, then we can execute them step by step with the support of VBScript Debug commands and Break points

Running tests

Generally, many companies are using Framework feature for Running Tests.

QTP Supports Individual Test execution, Batch execution, Tests execution through AOM Scripting, and Scheduled execution with the support of Windows Operating system.

Analyzing Results

It is not the Responsibility of QTP; Test engineer has to do this manually.

QTP is providing Result window in XML format.

QTP is providing Result deletion tool also.

QTP is providing Test results exporting facility. It supports HTML, Word document and PDF (portable document format) formats.

Reporting defects

Reporting defects also not a QTP responsibility that we have to do manually after analyzing the results, but if we are using Quality Center, from QTP result window we can send defects directly.

8) What types of License available for QTP?

a) Seat License or Node locked

Fixed for one System (Machine), we can use from that System only

b) Concurrent License or Floating License

This License, we can use from different Systems but one at a time

9) What are the QTP supported environments?

QTP Supports Software Applications based on Add-ins only

Add-in means Technology supporting files

QTP Add ins available for following technologies:

a) Default Add ins

1) Activex

2) Visual Basic

3) Web

b) Other Add-ins

1) Delphi

2) Java

3) .NET Web forms

4) .NET Windows forms

5) WPF (Windows Presentation Foundation)

6) Oracle

7) People Soft

8) Power Builder

9) SAP for Web

10) SAP GUI for windows environment

11) Siebel Environment

12) Standard Windows

13) Terminal Emulator (TE)

14) Visual Age Smalltalk Environment

15) Web Services Environment

10) Does QTP Support UNIX Environment?

No, QTP doesn’t support UNIX/Linux Environment, Supports Windows Operating Environment only, but LoadRunner and Quality Center have support both Windows and UNIX Operating Environments.

11) What is the scripting language that used in QTP for applying programming logic?

Micro Soft Visual Basic Scripting edition (VBScript) engine embedded with QTP.

12) Does QTP Support Database Testing and Data driven Testing?

Yes, SQL Engine embedded with QTP Tool, so we use SQL Statements directly in QTP Test Pane as well as in Function Library.

QTP has an integrated Spread sheet(Excel like) for Performing Data Driven Testing, otherwise we can fetch test data directly from external files and databases using VB Script.

QTP Interview Questions -2

1) What is Recording in QTP?

It is process of creating the main body of a test by recording the typical processes that users perform.

QuickTest records the operations we perform, displays them as steps in the Keyword View, and generates them in a script (in the Expert View).

2) How many Recording Modes available in QTP? What are they?

There are 3 Recording modes available in QTP.

1) Normal Recording

2) Analog Recording

3) Low Level Recording

3) What is Analog Recording mode?

It Records exact mouse and keyboard operations, we can use this mode for recording continues mouse operations like digital signatures, paints etc..

This mode doesn't generate statements for each and every operation, generates all operations in a Track file.

By default this mode is disabled, after selecting Normal Recording mode only it enables.

4) What is Low Level Recording?

It Records some operations on Non-supported environments apart from Normal operations.

5) What are object and Software Objects?

Object: Object is something, which has structure and properties.

Software Object: an object is any entity that can be manipulated by the commands of a programming language, such as a value, variable, function, or data structure.

Example:

GUI (Windows) Environment: Window, Dialog box, Edit Box, Button, Check Box, Radio Button, List Box and Combo Box etc...

Web Environment: Browser, Page, Link, Image, edit Box, Button, Grid, Frame Etc..

6) What type of Objects available in QTP?

There are 4 types of Objects available in QTP.

1) Run-time Objects

2) Test Objects

3) Utility Objects

4) Automation / User Defined Objects

7) What are Utility Objects?

These are QTP reserved objects, used for Testing and Result reporting.

Example:

a) SystemUtil

b) Reporter

c) DataTable

d) Services

e) environment etc...

8) What is Automation Object?

An object that is exposed to other applications or programming tools through Automation interfaces.

9) Explain about Object, Property and value?

Object: It is something which has structure and properties

Property: an attribute of an Object.

Value: Value of the Property

10) What is Object Repository?

It is a Storage place for Storing Objects, QTP has 2 types of Repositories.

a) Local Repository

b) Shared Repository

11) What are the differences between Local and Shared Repositories?

Local Repository:

QTP Creates a Local Repository for every Action during Recording automatically and also QTP maintenance Local Repositories, but user can edit these repositories.

It is a QTP Internal file, extension is .mtr

Shared Repository:

User Creates Shared Repositories by adding objects in Object Repository Manager.This can be shared among nuber of tests.

User has to maintain shared repository files

Shared Repository files are External files, extension is .tsr

12) How to Start Test Automation Process, before the Application is ready?

QTP is providing a feature called "Define New Test Object" for creating new objects without Application. This feature available in Local Repository and Object Repository Manager.

13) How to Combine Repositories?

We Can combine Repositories using Object Repository Merge Tool. It is available in Object Repository Manager

14) Explain about Statement, Action and Test in QTP?

a) Statement: an Instruction or a minimal executable unit

b) Action: Set of Statements

c) Test: One or more Actions

15) How Load repository files During run-time?

We can Load Object Repositories during run-time using an Utility object called "RepositoriesCollection"

Syntax:

RepositoriesCollection.Add "path of the Repository file"

Example:

RepositoriesCollection.Add "D:\ALOK\Login.tsr"

Business Process Testing : QTP

2011-10-03T03:41:00.000-07:00

This topic will guide you about BPT and how to work with BPT.
BPT Methodology

1) BPT is Business Process Testing

2) Additional module in QC and is known as Business Component

3) Test Scripts are associated with components.

4) Components are easily maintained, reusable units that perform a specific task.

QTP provides two types of components:

1) Business component

Business components (also known as keyword-driven components) are fully integrated with both QuickTest and Quality Center.

2) Scripted component

Scripted components are more complex components containing programming logic.

Pre-requisite for BPT:

1) Install BPT Add-Ins.

2) Check the “Allow the Mercury Products to run test and components”

checkbox in Options>Run tab.

BPT Strategy / Approach

1) Initially start with creating the scripted components from Business Component tab in QC.

2) Pull the respective components to the Test Plan from Component Folder in QC as per manual test case.

3) Pull the Test scripts to Test Lab for regressions.

4) Execute and Analyze the results and log the defects if any failure occurs.

Scripted Component:

Two ways to create a component

1) From QC> Go to Business Component tab> Click on New >Enter the component name > OK

2) From QTP> Connect to QC> New> Select Scripted Component>Enter the component name> OK.

Once after create the component in QC, we can find some tabs at right side pane in QC. Like Details, Snap shot, Design steps, Automation. We need to fill the information in these areas.

Details tab: Provides a general summary of the component’s purpose or

goals, and the condition of the application before and after a component is

run (its pre-conditions and post-conditions).

Snap shot tab: Displays an image that provides a visual cue or description of the components purpose or operations.

Parameter tab: Specifies the input and output component parameter values for the business component. Implementing and using parameters enables a component to receive data from an external source and to pass data to other components in the business process test flow.

Design Steps: Enables you to create or view the manual steps of your business component, and to automate it if required.

Automation tab: Provides access to automated component by choosing it to scripted component.

The component has 4 status:

1. Error: When Component is error for some reason like May be Test case is incorrect or May be made a mistake or May be created a wrong component, in such cases you set to “Error”

status and provide with meaningful comment, displayed in Red color.

2. Ready: Once the component is completed include debugging and enhancement then the component is Ready status, displayed in Green.

3. Under Development: When a new Component is to be created then the component is Under Development, displayed in Grey.

4. Maintenance: When the requirements changed then component is under Maintenance, displayed in Yellow

Parameterization:

Process to replace the constant values with variables is known as Parameterization.

There are 2 parameters:

1. Input Parameter:

With this parameter, you can input the data to the application.

This Input Parameter is also called “Component Parameter”

It’s another one more parameter especially for BPT apart from other parameters.

We can find this as “Component Parameter” from the list in Keyword View

Syntax is “Parameter(“<name of parameter>”)

2. Output Parameter:

With this parameter, you can retrieve the data from the application. Parameterization can be done in 2 ways for Input Parameters.

Application Area:

An application area, provides a single point of maintenance for all elements

associated with the testing of application. These include function libraries, shared

object repositories, keywords, testing preferences, and recovery scenarios.

From QTP>New > Application Area

Creation of Test Script

1) From Test Plan> Click New Test> Select BPT> Enter the name of

the script> OK

The icon will be created at left side panel.

2) Once created the script, List the all manual test cases, one which are related to this script under Details tab.

3) From Test Plan, pull the respective components under Test Script

Arrange the components in a work flow by moving the components up and down.

4) If the components have any parameters then displayed as link.

5) Click on this link, Component Iteration window will pop up. It just resembles the excel, where you enter the test data or import/export from external resource.

Regression Suite:

1) All the Test scripts are pulled to Test Lab for the regression testing.

2) Set to run the suite from one or more systems remotely.

3) Analyze the results.

Benefits of BPT Process

1) Each component is by default a reusable.

2) There is no concept of multiple actions. It means each component is single action.

3) Business process tests are created and implemented more quickly than other automated tests.

4) Reduces maintenance compared to traditional automation.

5) Data-driven testing can be performed effectively.

Scripting ADODB:QTP

2011-10-03T00:29:00.000-07:00

ADODB - Microsoft ActiveX Data Object 1. ADO is a Microsoft technology.
2. ADO stands for ActiveX Data Objects.
3. ADO is a Microsoft Active-X component
4. ADO is automatically installed with Microsoft IIS
5. ADO is a programming interface to access data in a database

ADO-ActiveX Data Objects
Microsoft® ActiveX® Data Objects (ADO) enable your client applications to access and manipulate data from a variety of sources through an OLE DB provider. Its primary benefits are ease of use, high speed, low memory overhead, and a small disk footprint. ADO supports key features for building client/server and Web-based applications.

RDS
Remote Data Service (RDS) is a feature of ADO, with which you can move data from a server to a client application or Web page, manipulate the data on the client, and return updates to the server in a single round trip.

OLEDB

OLEDB (sometimes written as OLEDB or OLE-DB) is an API designed by Microsoft for accessing different types of data stores in a uniform manner. It is a set of interfaces implemented using the Component Object Model (COM); it is otherwise unrelated to OLE. It was designed as a higher-level replacement for, and successor to, ODBC, extending its feature set to support a wider variety of non-relational databases, such as object databases and spreadsheets that do not
necessarily implement SQL. OLE DB separates the data store from the application that needs access to it through a set of abstractions, such as connections, record sets and attributes. This
was done because different applications need access to different types and sources of data and do not necessarily want to know how to access functionality with technology-specific methods. OLE DB is conceptually divided into consumers and providers. The consumers are the applications that need access to the data, and the provider is the software component that implements the interface. OLE DB is part of the Microsoft Data Access Components (MDAC) stack and is the database access interface technology. MDAC is a group of Microsoft
technologies that interact together as a framework that allows programmers a uniform and comprehensive way of developing applications for accessing almost any data store. OLE DB providers can be created to access such simple data stores as a text file or spreadsheet, through to such complex databases as Oracle, SQL Server and Sybase. However, because different data store technology can have different capabilities, OLE DB providers may not implement every possible interface available to OLEDB. The capabilities that are available are implemented through the use of COM objects - an OLE DB provider will map the data store technologies functionality to a particular COM interface. Microsoft calls the availability of an interface to be
"provider-specific" as it may not be applicable depending on the database technology involved. Additionally, however, providers may also augment the capabilities of a data store - these capabilities are known as services in Microsoft parlance.

ODBCThe Microsoft Open Database Connectivity (ODBC) interface is a C programming
language interface that makes it possible for applications to access data from a
variety of database management systems (DBMSs). The ODBC interface permits
maximum interoperability — an application can access data in diverse DBMSs
through a single interface. Furthermore, that application will be independent of any
DBMS from which it accesses data. Users of the application can add software
components called drivers, which interface between an application and a specific
DBMS.

The functions in the ODBC API are implemented by developers of DBMS-specific
drivers. Applications call the functions in these drivers to access data in a DBMSindependent
manner. A Driver Manager manages communication between
applications and drivers.

Applications that use ODBC are responsible for any cross-database functionality.
For example, ODBC is not a heterogeneous join engine, nor is it a distributed
transaction processor. However, because it is DBMS-independent, it can be used
to build such cross-database tools.

Connection.Open Method:
Syntax: object.Open (ConnectionString, UserID, Password, Options)

Connection.OpenSchema Method

Syntax: object.OpenSchema (QueryType, Criteria, SchemaID)

Example:
***************************************************************************

Option Explicit
Const adSchemaTables = &H14
Const adSchemaColumns = 4
Const adStateOpen = 1
Dim oConn, oRst, oRstSchema
Dim nRow
Dim sColumn
Set oConn = CreateObject("ADODB.Connection")
'--- Opening Database via DNS
oConn.Open "QT_Flight32"
'--- Open schema Tables
Set oRst = oConn.OpenSchema(adSchemaTables)
Do Until oRst.EOF
'--- Skip system tables
If StrComp(oRst("TABLE_TYPE").Value, "SYSTEM TABLE") <> 0 Then
sColumn = DataTable.LocalSheet.AddParameter( _
oRst("TABLE_NAME").Value, "").Name
'--- Querying Schema table columns
Set oRstSchema = oConn.OpenSchema(adSchemaColumns, _
Array(Empty, Empty, "" & oRst("TABLE_NAME").Value))
nRow = 1
DataTable.LocalSheet.SetCurrentRow nRow
Do While Not oRstSchema.EOF
DataTable(sColumn, dtLocalSheet) = _
oRstSchema("COLUMN_NAME").Value
oRstSchema.MoveNext
nRow = nRow + 1
DataTable.LocalSheet.SetCurrentRow nRow
Loop
End If
oRst.MoveNext
Loop
'--- Close the recordset schema if opened.
If oRstSchema.State = adStateOpen Then oRstSchema.Close
'--- Close the recordset if opened.
If oRst.State = adStateOpen Then oRst.Close
'--- Close the connection if opened.
If oConn.State = adStateOpen Then oConn.Close
Set oRst = Nothing : Set oConn = Nothing : Set oRstSchema = Nothing
***************************************************************************
OutPut:

OutPut:

Scripting Excel : QTP

2011-10-02T21:27:00.000-07:00

Drives, files and folders are the lifeblood of any organization; this makes file
system administration one of the most important responsibilities assigned to
system administrators. Of course, file system administration is also one of the
More difficult responsibilities to carry out, simply because files and folders are
Scattered on multiple hard disks and multiple computers throughout the
Organization. Scripts can help make file system management much easier,
Particularly when the files and folders managed, are located on remote computers.

1) Creating Excel Application Object

Syntax: Set ObjVar = CreateObject("Excel.Application")'Create
Examples: Excel ApplicationObject
Dim objExcel
Set objExcel = CreateObject("Excel.Application")
objExcel.Workbooks.Add
By running the preceding script, you really did create a brand-new instance of Microsoft Excel. Press CTRL-ALT-DEL and take a look at the Processes tab in the Task Manager. You should see an instance of Excel.exe

Examples:
-----------------------------------------------------------------------------------------
1) 'Create Excel file /Work book

Dim objExcel
Set objExcel = CreateObject("Excel.Application")
objExcel.Visible = True 'To make the excel visible
objExcel.Workbooks.Add ‘Adding a work book
objExcel.ActiveWorkbook.SaveAs "D:\ALOK\alok.xls"
objExcel.Quit
Set objExcel=Nothing ‘Releasing memory
-------------------------------------------------------------------------------------------------------

2)‘Checking for the existence of the file and entering some data into it
' If Not exists Create the Excel file /Work book and enter some data

Dim objExcel, objFso, FilePath
FilePath="D:\Alok\alok.xls"
Set objFso=CreateObject("Scripting.FileSystemObject")
Set objExcel=CreateObject("Excel.Application")

If objFso.FileExists(FilePath) Then
objExcel.Workbooks.Open (FilePath)
objExcel.Worksheets("Sheet1").Cells(1,1)="VB Script"
objExcel.ActiveWorkbook.Save
Else
objExcel.Workbooks.Add
objExcel.ActiveSheet.Cells(2,2)="VB Script"
objExcel.ActiveWorkbook.SaveAs (Filepath)
End If

objExcel.Quit 'To Quit the Excel Appliction
Set objExcel=Nothing
------------------------------------------------------------------------------------------------

3) 'Fetch Test Data directly from an Excel file and perform Data driven testing for Login Operation

Dim objExcel, objWorkbook, objWorksheet
'Create Excel application Object that can be used to perform operations on Excel Appliction
Set objExcel=CreateObject("Excel.Application")
'Create WorkBook Object using Excel application Object that can be used to perform operations on Excel Work Books
Set objWorkbook=objExcel.Workbooks.Open ("C:\Documents and Settings\Administrator\Desktop\input.xls")
'Create Work sheet object Using Work Book Object, that can be used to perform operations on Excel Sheets
Set objWorksheet=objWorkbook.Worksheets("Sheet1")
Rows_Count=objWorksheet.usedrange.rows.count

For i= 2 to Rows_Count Step 1
SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe","","C:\Program Files\HP\QuickTest Professional\samples\flight\app\","open"
Dialog("Login").Activate
Dialog("Login").WinEdit("Agent Name:").Set objWorksheet.Cells(i,"A")
Dialog("Login").WinEdit("Password:").Set objWorksheet.Cells(i,"B")
Wait 1
Dialog("Login").WinButton("OK").Click
Window("Flight Reservation").Close

Next
objExcel.Quit
Set objWorksheet=Nothing
Set objWorkbook=Nothing
Set objExcel=Nothing
-------------------------------------------------------------------------
4) 'Fetch Test Data directly from an Excel file and perform Data driven testing for Login Operation

'Export Test Results to the same file
Dim objExcel, objWorkbook, objWorksheet
'Create Excel application Object that can be used to perform operations on Excel Appliction
Set objExcel=CreateObject("Excel.Application")
'Create WorkBook Object using Excel application Object that can be used to perform operations on Excel Work Books
Set objWorkbook=objExcel.Workbooks.Open ("C:\Documents and Settings\Administrator\Desktop\input.xls")
'Create Work sheet object Using Work Book Object , that can be used to perform operations on Excel Sheets
Set objWorksheet=objWorkbook.Worksheets("Sheet1")
objWorksheet.Cells(1,3)="Results"
Rows_Count=objWorksheet.usedrange.rows.count

For i= 2 to Rows_Count Step 1
SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe","","C:\Program Files\HP\QuickTest Professional\samples\flight\app\","open"
Dialog("Login").Activate
Dialog("Login").WinEdit("Agent Name:").Set objWorksheet.Cells(i,"A")
Dialog("Login").WinEdit("Password:").Set objWorksheet.Cells(i,"B")
Wait 1
Dialog("Login").WinButton("OK").Click

If Window("Flight Reservation").Exist(12) Then
Window("Flight Reservation").Close
objWorksheet.Cells(i,"C")="Login Successful"
Else
SystemUtil.CloseDescendentProcesses
objWorksheet.Cells(i,"C")="Login Filed"
End If

Next
objWorkbook.Save
objExcel.Quit
Set objWorksheet=Nothing
Set objWorkbook=Nothing
Set objExcel=Nothing

5) 'Fetch Test Data directly from an Excel file and perform Data driven testing for Login Operation

'Export Test Results & Error Messgae to the same file
Dim objExcel, objWorkbook, objWorksheet, rows_Count

Set objExcel=CreateObject("Excel.Application")
Set objWorkbook=objExcel.Workbooks.Open ("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set objWorksheet=objWorkbook.Worksheets(1)

objWorksheet.Cells(1,3)="Test Result"
objWorksheet.Cells(1,4)="Error Message"

rows_Count=objWorksheet.usedrange.rows.count

For i= 2 to rows_Count Step 1
SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe","","C:\Program Files\HP\QuickTest Professional\samples\flight\app\","open"
Dialog("Login").Activate
Dialog("Login").WinEdit("Agent Name:").Set objWorksheet.Cells(i, 1)
Dialog("Login").WinEdit("Password:").Set objWorksheet.Cells(i, "B")
Dialog("Login").WinButton("OK").Click

If Window("Flight Reservation").Exist(12) Then
Window("Flight Reservation").Close
objWorksheet.Cells(i, 3)="Login Successful"
Else
objWorksheet.Cells(i, 3)="Login Failed"
objWorksheet.Cells(i, 4)=Dialog("Login").Dialog("Flight Reservations").Static("Agent name must be at").GetROProperty ("text")
SystemUtil.CloseDescendentProcesses
End If
Next

objWorkbook.Save
objExcel.Quit
Set objWorksheet=Nothing
Set objWorkbook=Nothing
Set objExcel=Nothing
6)
Using While...Wend Loop
------------------------
Dim objExcel, objWorkbook, objWorksheet, rows_Count, i

Set objExcel=CreateObject("Excel.Application")
Set objWorkbook=objExcel.Workbooks.Open ("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set objWorksheet=objWorkbook.Worksheets(1)

objWorksheet.Cells(1,3)="Test Result"
objWorksheet.Cells(1,4)="Error Message"

rows_Count=objWorksheet.usedrange.rows.count
i= 2
While i<= rows_Count
SystemUtil.Run "C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe","","C:\Program Files\HP\QuickTest Professional\samples\flight\app\","open"
Dialog("Login").Activate
Dialog("Login").WinEdit("Agent Name:").Set objWorksheet.Cells(i, 1)
Dialog("Login").WinEdit("Password:").Set objWorksheet.Cells(i, "B")
Dialog("Login").WinButton("OK").Click

If Window("Flight Reservation").Exist(12) Then
Window("Flight Reservation").Close
objWorksheet.Cells(i, 3)="Login Successful"
Else
objWorksheet.Cells(i, 3)="Login Failed"
objWorksheet.Cells(i, 4)=Dialog("Login").Dialog("FlightReservations").Static("Agent name must be at").GetROProperty ("text")
SystemUtil.CloseDescendentProcesses
End If
i=i+1
Wend

objWorkbook.Save
objExcel.Quit
Set objWorksheet=Nothing
Set objWorkbook=Nothing
Set objExcel=Nothing

7) 'Capture Link names from Google home page and export to Excel file3rd sheet

Dim ObjExcel,ObjWorkbook,ObjWorksheet
Dim oLink,Links,myLink,i

Set ObjExcel=CreateObject("Excel.Application")

Set ObjWorkbook=ObjExcel.Workbooks.Open("C:\Documents and Settings\Administrator\Desktop\input.xls")

Set ObjWorksheet=ObjWorkbook.Worksheets(3)
ObjWorksheet.Cells(1,1)="Link Names"
Set oLink=Description.Create

oLink("micclass").value="Link"

Set Links=Browser("title:=Google").Page("title:=Google").ChildObjects(oLink)

For i=0 to Links.Count-1 step 1

myLink=Links(i).GetRoProperty("text")
ObjWorksheet.Cells(i+2,1)=myLink
Next

ObjWorkbook.Save

ObjExcel.Quit

Set ObjWorksheet=Nothing

Set ObjWorkbook=Nothing

Set ObjExcel=Nothing
----------------------------------------------------------------------------------
8) 'Capture Button names from Login Dialog (Flight Reservation Application) and export to Excel file 3rd sheet

Dim ObjExcel,ObjWorkbook,ObjWorksheet
Dim oButton,Buttons,myButton,i

Set ObjExcel=CreateObject("Excel.Application")
Set ObjWorkbook=ObjExcel.Workbooks.Open("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set ObjWorksheet=ObjWorkbook.Worksheets(2)

ObjWorksheet.Cells(1,1)="Button Names"

Set oButton=Description.Create
oButton("Class Name").value="WinButton"
Set Buttons=Dialog("text:=Login").ChildObjects(oButton)

For i=0 to Buttons.Count-1 step 1
myButton=Buttons(i).GetRoProperty("text")
ObjWorksheet.Cells(i+2,1)=myButton
Next

ObjWorkbook.Save
ObjExcel.Quit
Set ObjWorksheet=Nothing
Set ObjWorkbook=Nothing
Set ObjExcel=Nothing
-----------------------------------------------------------------------------------
9) ' Read/capture order numbers and customer names from 1 - 10 orders in Flight Reservation window

' and export to excel file 2nd sheet
Dim objExcel, objWorkBook, objWorkSheet, ord, C_Name
Set objExcel = createobject("Excel.Application")
Set objWorkBook = objExcel.Workbooks.Open("C:\Documents and Settings\akm\Desktop\Sample.xls")
Set objWorkSheet = objWorkBook.Worksheets(2)
objWorkSheet.cells(1,1) = "Order No."
objWorkSheet.cells(1,2) = "C-Name"

For ord= 1 to 10 Step 1
Window("Flight Reservation").Activate
Window("Flight Reservation").WinButton("Button").Click
Window("Flight Reservation").Dialog("Open Order").WinCheckBox("Order No.").Set "ON"
Window("Flight Reservation").Dialog("Open Order").WinEdit("Edit").Set ord
Window("Flight Reservation").Dialog("Open Order").WinButton("OK").Click
Wait 1
C_Name = Window("Flight Reservation").WinEdit("Name:").GetROProperty("text")
objWorkSheet.cells(ord+1,1) = ord
objWorkSheet.cells(ord+1,2) =C_Name
Next

objWorkBook.Save
objExcel.Quit
Set objWorkSheet=Nothing
Set objWorkBook=Nothing
Set objExcel=Nothing

10) One to One Comparison and Exact match
----------------------------------------
'Capture Button names from Login Dialog (Flight Reservation Application) and Perform One to One Comparison and Exact match

Dim ObjExcel,ObjWorkbook,ObjWorksheet
Dim oButton,Buttons,myButton,i

Set ObjExcel=CreateObject("Excel.Application")
Set ObjWorkbook=ObjExcel.Workbooks.Open("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set ObjWorksheet=ObjWorkbook.Worksheets(2)

ObjWorksheet.Cells(1,2)="Buttons"

Set oButton=Description.Create
oButton("Class Name").value="WinButton"
Set Buttons=Dialog("text:=Login").ChildObjects(oButton)

For i=0 to Buttons.Count-1 step 1
myButton=Buttons(i).GetRoProperty("text")
ObjWorksheet.Cells(i+2, 2)=myButton
Next
rows_Count= ObjWorksheet.usedrange.rows.count
For j= 2 to rows_Count step 1
Expected=ObjWorksheet.Cells(j, 1)
Actual=ObjWorksheet.Cells(j, 2)

If Expected=Actual Then
ObjWorksheet.Cells(j, 3)="Pass"
Else
ObjWorksheet.Cells(j, 3)="Fail"
End If
Next

ObjWorkbook.Save
ObjExcel.Quit
Set ObjWorksheet=Nothing
Set ObjWorkbook=Nothing
Set ObjExcel=Nothing

11) One to One Textual Comparison
------------------------------
'Capture Button names from Login Dialog (Flight Reservation Application) and Perform and Perform One to One Textual Comparison

Dim ObjExcel,ObjWorkbook,ObjWorksheet
Dim oButton,Buttons,myButton,i

Set ObjExcel=CreateObject("Excel.Application")
Set ObjWorkbook=ObjExcel.Workbooks.Open("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set ObjWorksheet=ObjWorkbook.Worksheets(2)

ObjWorksheet.Cells(1,2)="Buttons"

Set oButton=Description.Create
oButton("Class Name").value="WinButton"
Set Buttons=Dialog("text:=Login").ChildObjects(oButton)

For i=0 to Buttons.Count-1 step 1
myButton=Buttons(i).GetRoProperty("text")
ObjWorksheet.Cells(i+2, 2)=myButton
Next
rows_Count= ObjWorksheet.usedrange.rows.count
For j= 2 to rows_Count step 1
Expected=ObjWorksheet.Cells(j, 1)
Actual=ObjWorksheet.Cells(j, 2)

If StrComp (Expected,Actual,1)=0 Then
ObjWorksheet.Cells(j, 3)="Pass"
Else
ObjWorksheet.Cells(j, 3)="Fail"
End If
Next

ObjWorkbook.Save
ObjExcel.Quit
Set ObjWorksheet=Nothing
Set ObjWorkbook=Nothing
Set ObjExcel=Nothing
--------------------------------------------------------------------------
12) Many to Many Comparison
-----------------------------------
'Capture Button names from Login Dialog (Flight Reservation Application) and Perform and Perform Many to Many Comparison

Dim ObjExcel,ObjWorkbook,ObjWorksheet
Dim oButton,Buttons,myButton,i

Set ObjExcel=CreateObject("Excel.Application")
Set ObjWorkbook=ObjExcel.Workbooks.Open("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set ObjWorksheet=ObjWorkbook.Worksheets(2)

ObjWorksheet.Cells(1,2)="Buttons"

Set oButton=Description.Create
oButton("Class Name").value="WinButton"
Set Buttons=Dialog("text:=Login").ChildObjects(oButton)

For i=0 to Buttons.Count-1 step 1
myButton=Buttons(i).GetRoProperty("text")
ObjWorksheet.Cells(i+2, 2)=myButton
Next
rows_Count= ObjWorksheet.usedrange.rows.count

For j= 2 to rows_Count step 1
Expected=ObjWorksheet.Cells(j, 1)

For k=2 to rows_Count step 1
Actual=ObjWorksheet.Cells(k, 2)

If Expected=Actual Then
Flag =1
Exit for
else
Flag= 0
End If
next

If Flag=1 Then
ObjWorksheet.Cells(j, 3)="Pass"
Else
ObjWorksheet.Cells(j, 3)="Fail"
End If
Next

ObjWorkbook.Save
ObjExcel.Quit
Set ObjWorksheet=Nothing
Set ObjWorkbook=Nothing
Set ObjExcel=Nothing

-------------------------------------------------------------------
13) Many to Many Textual Comparison

'Capture Button names from Login Dialog (Flight Reservation Application) and Perform and Perform Many to Many Textual Comparison

-----------------------------------
'Capture Button names from Google home page and export to Excel file 3rd sheet

Dim ObjExcel,ObjWorkbook,ObjWorksheet
Dim oButton,Buttons,myButton,i

Set ObjExcel=CreateObject("Excel.Application")
Set ObjWorkbook=ObjExcel.Workbooks.Open("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set ObjWorksheet=ObjWorkbook.Worksheets(2)

ObjWorksheet.Cells(1,2)="Buttons"

Set oButton=Description.Create
oButton("Class Name").value="WinButton"
Set Buttons=Dialog("text:=Login").ChildObjects(oButton)

For i=0 to Buttons.Count-1 step 1
myButton=Buttons(i).GetRoProperty("text")
ObjWorksheet.Cells(i+2, 2)=myButton
Next
rows_Count= ObjWorksheet.usedrange.rows.count

For j= 2 to rows_Count step 1
Expected=ObjWorksheet.Cells(j, 1)

For k=2 to rows_Count step 1
Actual=ObjWorksheet.Cells(k, 2)

If StrComp (Expected,Actual,1)= 0 Then
Flag =1
Exit for
else
Flag= 0
End If
next

If Flag=1 Then
ObjWorksheet.Cells(j, 3)="Pass"
Else
ObjWorksheet.Cells(j, 3)="Fail"
End If
Next

ObjWorkbook.Save
ObjExcel.Quit
Set ObjWorksheet=Nothing
Set ObjWorkbook=Nothing
Set ObjExcel=Nothing
---------------------------------------------------------------------------------------

14) 'Create Excel file and Rename 1st sheet as "Module", 2nd Sheet as "Test Case", 'and 3rd Sheet as "Test Step"
Dim objExcel
Set objExcel=CreateObject("Excel.Application")
objExcel.Visible=True
objExcel.Workbooks.Add
objExcel.Worksheets("Sheet1").Name="Module"
Wait 4
objExcel.Worksheets("Sheet2").Name="TestCase"
Wait 4
objExcel.Worksheets("Sheet3").Name="TestStep"

objExcel.ActiveWorkbook.SaveAs "C:\Documents and Settings\Administrator\Desktop\abcd.xls"

objExcel.Quit
Set objExcel=Nothing
-------------------------------------------------------------------------
15) 'Create an Excel file and add one more

Dim objExcel
Set objExcel=CreateObject("Excel.Application")
objExcel.Visible=True
objExcel.Workbooks.Add 'Creating Work Book
objExcel.Worksheets.Add 'Creating Work Sheet
Wait 4
objExcel.ActiveWorkbook.SaveAs "C:\Documents and Settings\Administrator\Desktop\abcde.xls"

objExcel.Quit
Set objExcel=Nothing
--------------------------------------------------------------------------------------
16) 'Capture Button names from Login Dialog (Flight Reservation Application) and perform Many to Many Complete Comparison

Capture Button names from Google home page and export to Excel file 3rd sheet

Dim ObjExcel,ObjWorkbook,ObjWorksheet
Dim oButton,Buttons,myButton,i

Set ObjExcel=CreateObject("Excel.Application")
Set ObjWorkbook=ObjExcel.Workbooks.Open("C:\Documents and Settings\Administrator\Desktop\input.xls")
Set ObjWorksheet=ObjWorkbook.Worksheets(2)

ObjWorksheet.Cells(1,2)="Buttons"

Set oButton=Description.Create
oButton("Class Name").value="WinButton"
Set Buttons=Dialog("text:=Login").ChildObjects(oButton)

For i=0 to Buttons.Count-1 step 1
myButton=Buttons(i).GetRoProperty("text")
ObjWorksheet.Cells(i+2, 2)=myButton
Next
rows_Count= ObjWorksheet.usedrange.rows.count

x =0

For j= 2 to rows_Count step 1
Expected=ObjWorksheet.Cells(j, 1)
flag = 0
For k=2 to rows_Count step 1
Actual=ObjWorksheet.Cells(k, 2)
If StrComp (Expected,Actual,1)= 0 Then
Flag =1
End If
x=x+1 ' increment the comparison count
next

If Flag=1 Then
ObjWorksheet.Cells(j, 3)="Pass"
Else
ObjWorksheet.Cells(j, 3)="Fail"
End If
msgbox x 'inner loop comparison values
Next
msgbox x ' Total number of comparisons

ObjWorkbook.Save
ObjExcel.Quit
Set ObjWorksheet=Nothing
Set ObjWorkbook=Nothing
Set ObjExcel=Nothing

Input/Out put Parameters:

2011-09-30T00:19:00.000-07:00

Input/Out put Parameters:

One can pass number of values in to the function while calling and a function can return only one value.

Example:

Function add(a,b) Main program
Res= a+b Add(10,20)
Add= res Msg box var
End function

Input/Output parameters concept is used for passing some values in to the action to return some values once the execution is finish
To do the same one has to declare the desired number of input parameters and out put parameters at the action, which is about to be called

Navigation:
• Activate the menu item test
• Select the option action properties
• Select the parameters tab
• Declare the desired number of input/output parameters
• Using the corresponding add buttons
• Click on OK

Exmaple:
vbwindow("Form1").VbEdit ("val1").set parameter ("a")
vbwindow("Form1").VbEdit("val2").Set parameter ("b")
vbwindow("Form1").VbButton("ADD").Click
var= vbwindow("Form1").VbEdit("res").GetROProperty "text"
parameter ("c")= var
vbwindow("Form1").Vbbutton("SUB").Click
var1=vbwindow("Form1").VbEdit("res").GetROProperty "textA"
parameter ("d")=var1
vbwindow("Form1").VbButton("CLEAR").Click

At the calling point one need to specify the input values in a sequence separated by commas and the variable names in a sequence in order to catch the return value

Example:Take the new test

Run action "action1[inout122]", one iteration,20,30,r1,r2
msg box r1
msg box r2

DataTable Methods

2011-09-30T00:13:00.000-07:00

QTP is having a powerful utility that is DataTable.It is normally used to enter the test data into the QTP script during script execution.
The following are some data table methods and their descriprions with examples.

Data table methods:

Data table methods are used for performing the operations on the runtime data table

1. Add- sheet: It is used for adding the new sheet for the runtime data table
SYNTAX: Data table.add sheet ”sheet name”

2. Delete- sheet: It is used for deleting a specified sheet from the run time data table
SYNTAX: Data table.delete sheet”sheet name”

3. Import: It is used for importing the data present in all the sheets in an excel file to the runtime data table
SYNTAX: Data table.import ”path of the excel file”

4. Import Sheet: It is used for importing specified sheet of data from the excel file to the specified sheet in the runtime data table
SYNTAX: Data table. Import sheet “path of the excel file, source sheet id, destination sheet id”

5. Export: It is used for exporting the complete data present in the run time data table to a specified location
SYNTAX: Data table. export “Path of the location with a file name.xls extension”

6.Export Sheet: It is used for exporting the data present in a specified sheet in the run time data table to a specified location
SYNTAX: Data table .export sheet “path of the location with a file name.xls extension”, sheet id to be exported.

7. Set currant row: It is used for making the QTP focus on a specified row
SYNTAX: Data table. Set currant row (row number)

8. Set next row: It is used for making the QTP focused on the next of the currently focused row
SYNTAX: Data table. Set next row

9.Set Prev Row: It is used for making the QTP focus on the previous row of the currently focused tow
SYNTAX: Data table. Set prev row

10. Value Method: It is used for getting a value from a specified sheet, specified column and currently focused row.
SYNTAX: Variable= Data Table. Value ( “column name”, sheet id)

11. Get Sheet: It is used for making the QTP to focus on a specified sheet
SYNTAX: Data table. Get sheet (sheet id)

12 Get Row Count: It is used for getting the row count of a global sheet
If at all one wants to get the row count of a specified sheet first of all they need to make the QTP to focus on a specified sheet and then get the row count
SYNTAX 1: Variable= Data Table. Get row count
SYNTAX 2: Variable= Data Table. Get sheet (“sheet id”). Get row count

Example:
DataTable.Addsheet “Alok”
DataTable.Importsheet “e:\Alok\td122.xls,1,3
N=Datatable.Getsheet( 3).getrowcount
For i= 1 to n
Data table. Setcurrantrow( i )
Vbwindow(“form1”).vbedit(“val1”).set datatable(“v1”,3)
Vbwindow(“form1).vbedit(‘val2’).set datatable(“v2”,3)
Vbwindow(”form1”).vbbutton(“add”).click
Expval= Datatable.value(“ev”,3)
Actval= vbwindow(“form1”).vbedit(“res”).getroproperty(“text”)
If (Expval= Actval) then
Datatable (“res”,3)= “pass”
Else
Datatable (“res”,3)= “fail”
End if
Next
Datatable.Export sheet “D;\fl_automation\log\file2.xls”,3
Datatable.Delete “Alok”

QTP Automation Architecture:-

2011-08-08T02:47:00.000-07:00

QTP Automation Process:

2011-08-08T02:37:00.000-07:00

Test Automation Framework:

2011-08-08T02:33:00.000-07:00

Automation Framework

Linear Framework:-
•It is a very simple framework.
•Only Record and Playback is done in this framework.
•It is a beginner level framework.
•Capturing tests by recording the actions of a manual tester.

Modular Framework:
•The whole scenario is divided into small business flows-called module.
•Those modules are written in a library file as a functions or reusable actions.
•Main Script is linked with small module functions or reusable actions, more over this is a very simple approach over record and play back.
•Modular is nothing but to make the script reusable.

Data Driven Framework:-
• Repeated use of Test Scripts with different inputs.
• Separates out the test inputs (the data), usually into a spreadsheet, and uses a more generic script that can read the test data and perform the same test with different data.
• Testers who are not familiar with the scripting language can enter test data for these predefined scripts.
• Ease of Testing of Time consumption.

Keyword Driven Framework:-
• Steps and data are feed to the automation tool.
•Automation tool judges the steps and input data from a data pool, It gave the output data
•Spreadsheet contains keywords describing the actions to be taken (also called action words), and test data.
• Testers (even if they are not familiar with the
scripting language) can then define tests using the keywords.
• Very sensitive towards data.

Hybrid Framework:-
• Combination of keyword, data driven and modular framework.
• The main advantage is this is logic driven.
• Keywords are logic based.

Automation Testing

2011-08-08T02:22:00.000-07:00

Automation Testing:-

•Testing software using software known as automation testing.
•Framework is a set of rule designed by the experts.
•There is no hard and fast rule to design a framework.
•Currently, IT industry has various frameworks in support of automation testing.

1) Linear Framework
2) Modular Framework
3) Data Driven Framework
4) Keyword Driven Framework
5) Hybrid Framework

Sample Questions-Part 2-QTP

2011-07-28T03:27:00.000-07:00

1) Which scripting language is used in QTP ?

Test Script Language (TSL)
Java Script
ASP
VB Script

2) Does QTP support Data Driven Framework ?

YES
QTP supports only Modular Framework
QTP is only Keyword Driven Framework
No

Amazon.com Widgets

3) Select the Browsers NOT Supported by QTP ?

IE
Netscape
Safari
AOL

4) “Active Screen” Technology in QTP gives

Test Data
Checkpoints
Screenshots of Application Under Test (AUT)
Object Repository

5) Does the “Information” Toolbar in QTP 10.x give the Syntax Errors if any in the script ?

YES

It gives syntax errors only related to functions

6) Method to To count the no of rows in a table

getrowcount

getlinecount

Getcount

Count

7) Select Case statement is end with

end case

exit case

esac

end select

8) Object Repository is available in 3 modes viz.a) Per-Action Object Repository b) Shared Object Repository, c) Unshared Object Repository

Both a & b

Both a & c

Both b & c

Only a

9) What is the correct order of events in Test Script Creation ?

Plan, Record , Debug, Enhance

Plan , Record , Enhance , Debug

Record, Debug , Plan , Enhance

Record, Enhance, Debug , Plan

10) Which one is the default data type of QTP

integer

String

Variant

Double

11) To use the non-standard windows object, we can go for

Object spy

Virtual objects

Object identification

None

12) Select INVALID Checkpoint Type from the following

Page Checkpoint

Accessibility Checkpoint

Object Checkpoint

XML Checkpoint

13) To terminate the script execution, during running, QTP uses

Exit run

Stop run

Quit

None

14) BITMAP Checkpoint checks the property values of an image ?

YES

15) Synchronization Point is used :-

To delay QTP execution until Application Under Test (AUT) attains certain status

To synchronize execution in multiple instances of QTP

To synchronize per action and shared object repositories

16) Do statement always end with

end while

End do

Wend

Loop

17) By default a Datable contains :-

One Action Sheet and One Global Sheet

Two Global Sheets

Two Action Sheets

Two Action Sheets and One Global Sheet

18) Results Table (results of a test) is available in which following locations ?

Test Script Folder

Test Configuration Folder

Test Results Folder

Test Functions Folder

19) *.mts file contains :-

Sequence and iterations of Actions to be executed

User created library functions

Per-Action Object Repository Files

Parameter used in Actions

20) The feature of selecting different values of test data at run-time is called

Synchronization

Parameterization

Smart Identification

Transaction

21) Can Checkpoints be parameterized ?

YES

Maybe. Depends on the type of checkpoints

22) Can Test-Data in “Action Sheet” of Data Table be used from one action to another ?

YES

23) Text Output Value -

a) outputs property value of any object

b) outputs text string appearing in AUT

c) outputs part of displayed text appearing in AUT

only a

only b

only c

both b & c

24) Select the valid types of Actions in QTP

a) Nested Actions

b) Shared Actions

c) External Actions

d) Reusable Actions

both b & c

both b & d

both a & d

both a & c

25) Can Actions inserted as “Call to Action” be modified by the test engineer?

YES

26) Action Sheet (in Data Table) of an action inserted as “Copy of an Action” is editable only from the test from which they were created ?

YES

27) Action Iteration is :-

Number of times action would be executed every global iteration

Number of time action would be executed in entire test execution

Number of times all actions would be executed globally.

28) Choose the valid syntax to call Action 1 ( from Action 0) with input parameter “action_in” and store the output in a variable “MyVariable”

RunAction 'Action1', oneIteration, Parameter(“action_in”), MyVariable

RunAction 'Action0', oneIteration, Parameter(“action_in”), MyVariable

RunAction 'Action1', oneIteration, MyVariable , Parameter(“action_in”)

RunAction 'Action0', oneIteration, MyVariable , Parameter(“action_in

29) Can we use all standard Microsoft Excel features like Formulae, Formatting , Sorting etc in QTP DataTable ?

YES

30) “Call to Copy” of an action can be inserted only for reusable actions ?

YES

31) Parameterization of all Test data in a script can be done using

Object Repository Manager

Virtual Object Manager

Data Driver

Variable Driver

32) Are Nested Actions Call to one Action from Another ?

YES

33) Is the Shared ( Global ) Action Repository the default repository in QTP ?

YES

34) In a Per – Action (Local) Repository Action 1 and Action 2 in the same test script would have different object repositories?

YES

35) The Share Action Repository is preferable when

The Application Under Test is Dynamic with respect time

The Application Under Test is Internet Environment

The Application Under Test is Static

36) What is *.tsr file in QTP ?

Object Repository Files

VB Actions Files

QTP Action Files

Stores Test Data

37) Object Spy can be used to

identify the Objects that can be identified by QTP

identify the properties used for identification of objects

identify the properties used for identification of objects in per-action repository

identify the properties used for identification of objects in global action repository

38) Are Assistive properties used when mandatory properties are enough to identify an object ?

YES

39) Are Ordinal Identifiers used when Mandatory and Assistive properties used by QTP are not enough to identify Object?

YES

40) Select the Invalid type of Ordinal Identifiers Used by QTP

Index Based

Location based

Creation Time

Time Based

41) Does Index based ordinal identifier indicates the order in which the object appears in the parent window frame or dialog box relative to other objects?

YES

42) Does Location based ordinal identifier indicates the order in which object appears in the application code relative to other objects?

YES

43) Select the environments in which Creation Time ordinal identifier is used

SAP

Oracle

Web

Java

44) When a test is run in update mode, what is updated?

The test results

The object descriptions

The action names in the test

The logical names in the test

45) For identification of any object the choice of ordinal identifier selected can be modified in the Object Identification Window?

YES

46) The Index Property value of Occurrence of the first object in source code is

47) Is Smart Identification is invoked when QTP cannot recognize an object using mandatory , assistive and ordinal properties ?

Yes

Only in Web Environments

48) Select the type of properties used for Smart Identification

Mandatory Properties

Assistive Properties

Base Filter Properties

Smart Properties

49) Utility to measure the timing delays between transactions, we use

synchronization

sync

services

wait

50) Select the Invalid recording modes supported by QTP

Low-level Recording mode

Normal recording mode

High-level Recording mode

Analog recording mode

51) What does a breakpoint do?

Stops test execution at the specified step, after executing that step

Stops test execution at the specified step, before executing that step

Pauses test execution at the specified step, after executing that step

Pauses test execution at the specified step, before executing that step

52) Does Analog Recording mode, records exact mouse and keyboard operations ?

YES

53) The RunAnalog function is used to run

Tracks

Functions

Analog Functions

Analog settings

54) Consider the QTP Script below

Window(“Calculator”).WinObject(“8”).Click 21,6

Window(“Calculator”).WinObject(“WinObject”).Click 14,13

In which mode is the script recorded ?

Analog Recording mode

Context Sensitive mode

Low Level Recording mode

55) Virtual Objects are used when:-

The objects do not exist in the Application Under Test

Standard Objects cannot be recorded due to problems that arise during recording

There are many objects of the same class in the Application Under Test

56) Consider the QTP Script below:-

On Error Resume Next

What does the above line of code do ?

If an error occurs in the current line of script under execution , QTP proceeds ahead to the next step

If an error occurs in the current iteration in script execution , QTP proceeds ahead to next iteration

57) Which of the following is an example of a missing resource?

An object

Run Results

A Regular Action

An External Action

58) To enter the non-executable statement in QTP , we use

single quotes

Rem

double quotes

Com

VB Script:QTP

2011-07-19T03:07:00.000-07:00

As we all are aware that QTP supports VB script.

VB script: Basic

A variable is a virtual container in the computer's memory where we can store

Program information that may change during the time of our script is running.

In VBScript, variables are always of one fundamental data type, Variant.

A computer program can store information in a variable and then access that

Information later by referring to the variable's name.

Dim Statement

The Dim statement declares and allocates storage space in memory for

Variables. If the Dim statement is used at the start of a procedure then the variable is local to the procedure, if it is used at start of a global script block the Dim will available throughout the module.

Syntax: Dim varname[([subscripts])][, varname[([subscripts])]]

Option Explicit Statement

Forces explicit declaration of all variables in a script.

If used, the Option Explicit statement must appear in a script before any other

statements. When you use the Option Explicit statement, you must explicitly

declare all variables using the Dim, Private, Public, or ReDim statements. If you

attempt to use an undeclared variable name, an error pop will appear displaying the message as “variable is undefined”

Arrays:

It is a variable which contains a series of variables value. Array variables and scalar variables are declared in the same way, except that the declaration of an array variable uses parentheses ( ) following the variable name. Arrays are useful when we are storing sets of similar data.

Constants

A constant contains a value that never changes. For example, the value of PI is a constant. Use constants to define values that you know will never change during the execution of your script.VBScript also allows you to define your own constants.

Descriptive programming in QTP

Whenever QTP records any action on any object of an application, it adds some description on how to recognize that object to a repository of objects called object repository. QTP cannot take action on an object until unless its object description is in the Object Repository. But descriptive programming provides a way to perform action on objects which are not in Object repository.

Why to use Descriptive programming?
Below are some of the situations when Descriptive Programming can be considered useful:
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 <<UserName>>”.
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.
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.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.
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.

How to use Descriptive programming:

There are two ways in which descriptive programming can be used
By creating properties collection object for the description.
By giving the description in form of the string arguments.By creating properties collection object for the description.To use this method you need first to create an empty description

Control Structures

Control structures allow you to control the flow of execution of your scripts. You can specify that some code should be executed only under certain circumstances, using conditional structures. You can specify that some code should be executed repeatedly, using looping structures. Lastly, you can specify that code from somewhere else in the script should be executed using branching structures.

Conditional Structures

A) If...Then...Else:

It allows you to choose which block of code to execute based on a condition or series of conditions.

If condition1 Then
  code block 1
ElseIf condition2 Then
  code block 2
Else
  code block 3
End If

If condition1 is True, code block 1 is executed. If it is False, and condition2 is True, code block 2 is executed. If condition1 and condition2 are False, code block 3 executes.
An If...Then construct may have zero or more ElseIf statements, and zero or one Else statements.
You can use NOT to reverse the logic of the IF structure. (i.e. If Not...Then...Else)

B) Select Case:

It can be used instead of using some really complex If...Then constructs.

Select Case variable
Case chioce1
  code block 1
Case choice2
  code block 2
...
Case choiceN
  code block N
Case Else
  default code block
End Select

This compares the value of variable with choice1, choice2, and so on. If it finds a match, it executes the code block associated with that choice. If it does not find a match, it executes the default code block.

Looping Structures

Looping structures allow you to execute the same block of code repeatedly. The number of times it executes may be fixed or may be based on one or more conditions. Be careful not to create an endless loop; that is one where the condition required to break the loop is never met.

A) For...Next :

The looping structures take the following form:

For counter = start to s
code block
Next

code block is executed with counter having the value start, then again with counter having the value start+1, then start+2, and so on until it has the value s. It then leaves the loop.

Optionally, you may specify a different value to increment counter by using this construct:

For counter = start to s Step stepvalue
code block
Next

counter will take the values start+stepvalue, for example if stepvalue is 2 counter will count by 2s. If stepvalue is negative, s should be less than start.

B) For Each...Next :

The loop use the following form:

For Each item In set
code block
Next

code block is executed with item taking the value of each member of set. set should be an array or a collection.

C) Do...While looping structure:

Do While booleanValue
codeblock
Loop

code block is executed as long as booleanValue is True. If it is False to begin with, the loop is not executed at all.

D) While...Wend looping structures have the following form :

while booleanValue
code block
Wend

code block is executed as long as booleanValue is True. If it is False to begin with, the loop is not executed at all. Note: Wend is not supported in ASP.NET; use End While instead.

E) Do...Loop While looping structure:

Do
code block
Loop While booleanValue

code block is executed as long as booleanValue is True. The loop is executed at least once no matter what.

F) Do Until...Loop looks like this:

Do Until booleanValue
code block
Loop

code block is executed as long as booleanValue is False. If it is True to begin with, the loop is not executed at all.

G) Do...Loop Until uses the following form:

Do
code block
Loop Until booleanValue

code block is executed as long as booleanValue is False. The loop is executed at least once no matter what.

Branching Structures:

Branching structures allow you to jump from one position in the code to another.

Subroutines:

It do not return a value. They simply execute.

Sub name (argumentlist)
code block
End Sub

Functions:

It return a value and have the following form:

Function name (argumentlist)
code block
name = expression
End Function

Sample Questions in QTP

2011-07-19T02:13:00.000-07:00

Sample Questions:

1. What does ChildObject Method Return
a. A Collection Object
b. A string true/false
c. A Boolean True/False
d. The Number of objects matching the child object descriptions
Ans: a

2. How can you make a test bypass the Object Repository during Test Run.
a. Turn the Object Repository Off
b. Use a programmatic Description
c. Delete all objects in all repositories
d. Add the Object in Object Repository Manager
Ans: b

3. When a test is run in Update mode, what options can you select? Select Three
a. the datatable
b. Check point properties
c. Test Object Description
d. Action Names in the test
e. Logical Names in the test
f. Active Screen Images and Values
Ans.C
4. What Object is used to read information from text file
a. Read
b. ReadLine
c. TextStream
d. FileStream
e. OpenTextFile
Ans.b

5. What can you use to handle unpredictable exceptions
a. A Do Loop
b. Recovery Scenario
c. If Then Else
d. Select Case Statemtn
Ans: b

6. You have just stopped recording steps into your tests. Your application under step is still up and visible on your screen. You now wish to add checkpoints into your test using the menu command, insert > Checkpoint from the toolbar. Which checkboxes are available to you? Select two
a. Text checkpoint
b. XML checkpoint
c. Bitmap checkpoint
d. TextArea checkpoint
Ans:b
7. Browser Navigation Timeout is in which tab of Test Settings
a. Properties
b. Resources
c. Web
d. Web Settings

Ans: c

8. How many tabs are present in Test Settings (File > Settings) window
a. 7
b. 6
c. 5
d. 8
Ans: a

9. Identify the Tabs in the Test Settings (File > Settings) Window
a. Properties, Run, Resources, Parameters, Environment, Web, Recovery
b. Properties, Run, Resources, Parameters, Environment, Web Settings, Recovery
c. Properties, Run, Options, Parameters, Environment, Web, Recovery
d. Properties, Run, Resources, Input Parameters, Environment, Web, Recovery
Ans: a

10.'Generate Script' is in which tab of Test Settings (File > Settings) window
a. Properties
b. Web
c. Resources
d. Recovery
Ans: a

11. The following are the main columns in the Keyword view
a. Item, Operation, Value, Comments
b. Item, Operation, Value, Documentation
c. Item, Operation, Property, Documentation
d. Number, Operation, Value, Documentation
Ans: b

12. For each object and method in an Expert view statement, a corresponding row exists in the Keyword view
a. True
b. False
c. There is a problem with the statement
d. None of the above
Ans: a

13. You can work with one or several function libraries at the same time
a. True
b. False
Ans: a

14. You can insert additional steps on the test objects captured in the Active Screen after the recording session
a. True
b. False
Ans: a

15. Active screen enables you to parameterize object values and insert checkpoints
a. True
b. False
Ans: a

16. A QTP user can increase or decrease the active screen information saved with the test.
a. True
b. False
Ans: a

17. The information pane provides a list of ... in the test.
a. Semantic error
b. Syntax error
c. Common errors
d. Logical errors
Ans: b

18. When we switch from Expert view to Keyword view, QTP automatically checks for syntax errors and shows them in the information pane.
a. True
b. False
Ans: a

19. If the information pane is not open, QTP automatically opens it incase a syntax error is detected
a. True
b. False
Ans: a

Regular Expression in QTP

2011-07-12T08:20:00.000-07:00

I found regular expression concept in QTPro is a very strong concept.I found it is very much helpful in web application.In web applicatiton the web object are changed dynamic.Now i am going to describe the regular expression.I found some useful content regarding the regular expression and their use while i was exploring some sites.

Regular Expression:

A regular expression is a formula for matching strings that follow some pattern.

In QuickTest Regular Expressions can be used in 3 places:

1) Object Repository

2) CheckPoints

3) RegExp object.

Navigation through OR in QTP

· Open the object repository

· Select the desired object in the object hierarchy

· Select the desired property in the properties list

· Click on the constant value options button

· Replace the constant value with suitable regular expression

· Select the check box regular expression

· Click on ok

There's a good reason that regular expressions are found in so many diverse applications: they are extremely powerful. At a low level, a regular expression describes a chunk of text.

RegularExpression Cheat Sheet

Debugging

2011-07-11T08:08:00.001-07:00

The following is the debugging process and the operational overview of the different step command available during debugging

Debugging:

Debugging is a process of executing the script or a program in a user desired passion with some temporary breaks in order to identify the errors.

To do the same QTP has provided step commands and break point feature.

Step commands: -

Step into
Step Out
Step over

1. Step into:

Step into is used for executing a single statement then it will step in to the function or action and stops the execution.

2. Step Out:

Step out is used for executing all the remaining statements from the position of pointer in the function of the action and comes out of the function or action and stops execution

3. Step Over:

Step over is used for executing the single statement if that statement is a function call or action call then it will execute all the statements in side the function or action once and stops the execution

Break Point:

Break point is the feature provided by QTP, which is used for breaking the execution temporarily.

Debug viewer Pane:

Debug viewer pane is used for viewing, modifying or setting the currant value of the variables or expressions during the execution break with the help of three tabs by name

Watch expressions
Variables
Command

Reporter utility object

2011-07-11T08:00:00.001-07:00

Reporter utility object: -

It is used for reporting an user defined message to the result window

SYNTAX:

Reporter.Reportevent status,”object name”,”message”

Example: Reporter.Reportevent micdone,”my report”,”add button is working fine”.

Status:

Pass	0
Fail	1
Done	2
Warning	3

Transaction point in QTP

2011-07-11T07:51:00.003-07:00

Transaction point:

It is a concept introduced in QTP which is used for calculating the time taken by an application to perform a specific task or the execution time of a block of statement.

QTP has provided the following transaction options.

Start transaction
End transaction

Syntax:

Services.start transaction ”transaction name”

“ statement 1”

“ statement 2

Services.end transaction ”transaction name”

OUT PUT VALUE in QTP:

2011-07-11T07:39:00.000-07:00

OUT PUT VALUE: -

Out put value is a feature provided by QTP, which is used for capturing a value from an application or from a database or from a XML file and stores it under specified column in the runtime data table

Operational overview of out put value: -

The out put value feature works in the following phases

Pre-Execution Phase
While –Execution Phase

1. Pre-Execution phase:

It will capture the field name from which it need to capture the value

It will generate the corresponding script

2. While-Execution phase:

Captures the actual value from the field

Stores it under a specified column in the run time data table

Out Put Values-

There are the following types of out put values

Standard Out Put Value: - It is used for capturing property value of a standard GUI object.
Text Out Put Value: - It is used for capturing the text present on a specified object
Text-Area Out Put Value: - It is used for capturing the Text present in a specified area
Data Base Out Put Value: - It is used for capturing a value from the database
XML Out put Value: - It is used for capturing a value from the XML file

Navigation for Standard Out put value through application:

Keep the cursor in the desired location
Keep the tool under recording mode
Activate the menu item insert
Go to out put value
Select the option standard out put value
Click on the desired object in the AUT
Click on OK
Select the desired property to be captured
Click on modify
Specify the desired column name
Click on Ok
Once again click on ok
Stop recording

Navigation For standard check point through Active Screen

Keep the cursor under the desired location
Click on active screen
Right click on desired location
Click on insert output value
Click on ok
Select the desired property
Click on modify
Specify the desired column name
Click on ok
Once again click on ok.

Data Driven Testing in QTP:

2011-07-11T07:29:00.001-07:00

Data Driven Testing

Data driven testing is a concept introduced in the automation in order to implement re- testing.

Steps to be followed to perform data driven testing:

Collect the test data in to the data table
Generate the basic test
Parameterize the test
Execute the Test
Analyze the result

Parameterization:

Parameterization is a process of replacing the constant values with parameters or variables in order to increase the scope of the test. Parameterize can be done in three ways

Through data driver wizard
Through key word view
Manually

Navigation through Data Driver Wizard:

Activate the menu item tools
Select the option data driver
Click on parameterize
Click on next
Click on the parameter option button
Select the desired column name
Click on ok
Click on next
Click on finish
Finally click on ok

Navigation Through Key word view:

Go to key word view
Select the desited constant value
Click on configure the value button
Select the option parameter
Select the desired column name
Click on ok

To avoid the above navigation one can directly type manually as follows:

A= datatable(“v1”,1)

Vbwindow(“form1”).vbedit(“val1”).set A

Vbwindow (“form1”).vbedit(“val2”).set datatable(“v2,1)

Vbwindow(“form1”).vbbutton(“Add”).Click

Vbwindow(“form1”).vbedit(“res”).check checkpoint(“RES”)

Navigation for parameterizing the check point:

Right click on the check point statement
Select the option check point properties
Select the option parameter
Click on the parameter options button
Select the desired column name
Click on ok
Once again click on ok

We can also parameter the test objects from object repository/object repository manager.