Friday, 25 November 2011

Car Info

After months of speculation and spy shots, Maranello has finally revealed the mid-engined V8 replacement for the Ferrari F430. The all-new Ferrari 458 Italia won't be shown in public until September's Frankfurt Motor Show, but the official details were released early this morning. A new direct-injected 4.5-liter V8 ups the ante underhood, pumping out 562 horsepower and 398 lb-ft of torque. The redline? A screaming 9,000 rpm. Eighty percent of the F458 Italia's torque is now available at a low 3,250 rpm, thanks in all likelihood to the new engine's 12.5:1 compression ratio.

As with last year's California, the Ferrari 458 gets a seven-speed dual clutch gearbox that directs power to the rear axle. Much has been done to reduce internal friction within the new V8, in addition aerodynamic drag improvements. As a result, the Ferrari 458 Italia's gas mileage improves to a combined 17.1 mpg (US) on the EU test cycle. As this is a Ferrari, talk of fuel consumption really does seem somewhat pointless, anyway. No mention of incorporating any type of KERS hybrid system has been made thus far. The KERS idea, you'll remember, had taken several spins around the rumormill over the last year or so; maybe that'll materialize at a later date.

Like its predecessor, the Ferrari 458 Italia's aluminum structure helps keep weight under control -- it tips the scales at just 3,042 pounds dry. So, we know you're wondering: How quick is it? Based on specs at least, this new coupe does't disappoint. Acceleration to 100 km/h (62 mph) takes just 3.4 seconds, and this will be the first volume production Ferrari V8 to top the 200 mph barrier, with a top whack of 202 mph. Is it still too early to head to the airport for our flight to Frankfurt in September?

[Source: Ferrari]

ITALIA - Ferrari's innovative new V8

The 458 Italia is the latest incarnation of the mid-rear engined berlinetta and will be unveiled at the next Frankfurt Motor Show

Maranello, July 28th 2009 – While it's true that every Ferrari is innovative by definition, it's equally true that in the course of the Prancing Horse's history, certain cars have marked a genuine departure from the current range. This is very much the case with the Ferrari 458 Italia, which is a massive leap forward from the company's previous mid-rear engined sports cars.

The new model is a synthesis of style, creative flair, passion and cutting-edge technology, characteristics for which Italy as a nation is well-known. For this reason Ferrari chose to add the name of its homeland to the traditional figure representing the displacement and number of cylinders.

The Ferrari 458 Italia is a completely new car from every point of view: engine, design, aerodynamics, handling, instrumentation and ergonomics, just to name a few.

A two-seater berlinetta, the Ferrari 458 Italia, as is now traditional for all Ferrari's road-going cars, benefits hugely from the company's Formula 1 experience. This is particularly evident in the speed and precision with which the car responds to driver inputs and in the attention focused on reducing internal friction in the engine for lower fuel consumption than the F430, despite the fact that both overall displacement and power have increased. However, Ferrari's track experience makes its presence felt in the 458 Italia not only in terms of pure technological transfer but also on a more emotional level, because of the strong emphasis on creating an almost symbiotic relationship between driver and car. The 458 Italia features an innovative driving environment with a new kind of steering wheel and dashboard that is the direct result of racing practice. Once again input from Michael Schumacher - who was involved from the very start of the 458 Italia project - played an invaluable part.

The Ferrari 458 Italia's Pininfarina design provides further evidence of the complete departure from the past that this new car hails. The Ferrari 458 Italia has a compact, aerodynamic shape, underscoring the concepts of simplicity, efficiency and lightness that inspired the project. As with every Ferrari, the car's styling has been very heavily influenced by the requirements for aerodynamic efficiency, as can be seen from the downforce of 140 kg at 200km/h generated by the new model. The front features a single opening for the front grille and side air intakes, with aerodynamic sections and profiles designed to direct air to the coolant radiators and the new flat underbody. The nose also sports small aeroelastic winglets which generate downforce and, as speed rises, deform to reduce the section of the radiator inlets and cut drag.

The new 4499 cc V8 is the first Ferrari direct injection engine to be mid-rear mounted. It has a very low piston compression height typical of racing engines which contributed to achieving its compression ratio of 12.5:1. Equipped with the traditional flat-plane crankshaft, the engine delivers 570 CV at 9000 rpm and, with an outstanding power output of 127 CV/litre, sets a new benchmark not only for the whole Ferrari range and the history of company, but also for the entire market segment. Maximum torque is 540 Nm at 6000 rpm, over 80 per cent of which is available from 3250 rpm. Specific torque is a record 120 Nm/litre. However, what is truly extraordinary is the amount of torque available while still maintaining high levels of power at low revs.

The car's soundtrack is also typical Ferrari, with an exciting, powerful growl emerging from the engine before it channels through to the exhaust's three rear tailpipes.

The 458 Italia is equipped with the seven-speed dual-clutch transmission which increases performance whilst providing very smooth shifts even at full throttle. The engineers have developed specific, sportier gear ratios to match the power and torque curves of the new V8, guaranteeing high torque even at lower engine speeds and allowing the car to reach its maximum speed in top gear.

This new Ferrari is also a major leap forward when it comes to cutting emissions. Despite the fact that the new engine is significantly more powerful than the V8s that preceded it, the Ferrari 458 Italia produces just 320 g/km of CO2 and fuel consumption is 13.7 l/100 km (combined cycle), the best in the entire segment.

The engineers also focused on weight reduction during the design phase for similar reasons. Consequently, the Ferrari 458 Italia has a dry weight of 1380 kg with a power-to-weight ratio of 2.42 kg/CV. Weight distribution is also optimal with 58 per cent over the rear axle. The result of the engineers' endeavours can be summed up in to two simple statistics which together perfectly encapsulate the Ferrari 458 Italia's exceptional performance: 0-100 km/h acceleration in under 3.4 seconds and a maximum speed in excess of 325 km/h.

For the new chassis, once more in aluminium, Maranello's engineers incorporated various types of advanced alloys along with aerospace industry-derived manufacturing and bonding techniques.

With regard to vehicle dynamics, the Ferrari 458 Italia's suspension features twin wishbones at the front and a multi-link set-up at the rear tuned for maximum roadholding and superlative handling. Along with a more direct steering ratio, the 458 Italia thus offers extremely rapid turn-in and body control whilst maintaining superior ride comfort.

The integration of the E-Diff and F1-Trac (now controlled by the same ECU) and their respective mappings is even greater, resulting in a 32 per cent increase in longitudinal acceleration out of corners compared to previous models. The evolution of the control logic, with even faster and more accurate calculation of levels of grip, ensures even greater roadholding, better handling and ease of control on the limit.

The same ECU also governs the high-performance ABS, providing even more precise control over the logic threshold and greater efficiency. The brakes also feature a prefill function whereby the pistons in the callipers move the pads into contact with the discs on lift off to minimise delay in the brakes being applied. This combined with the ABS has cut the 100-0 km/h braking distance to a mere 32.5 metres.

The Ferrari 458 Italia's interior is another area of the car that exalts its sporty personality. The driver is welcomed by a new layout and a revolutionary ergonomic interface where the main controls are all clustered on the steering wheel.

With the Ferrari 458 Italia, Maranello has brought a highly distinctive new car to its 8-cylinder range. The company now offers two models that share a common, race-derived DNA, both exceptionally sporty and fun to drive in true Ferrari tradition, but aimed at two very different kinds of client. While the Ferrari California was created for owners requiring a more versatile sports car with a practical edge, the 458 Italia is designed for owners for whom the priority is uncompromising on-road performance with occasional track day capability, but who still demand a car that is useable in day-to-day driving like all Ferrari's recent models.


Ferrari 458 Italia – Technical specifications

Dimensions

Length 4527 mm (178.2 in.)

Width 1937 mm (76.3 in.)

Height 1213 mm (47.8 in.)

Wheelbase 2650 mm (104.3 in.)

Dry weight 1380 kg (3042 lbs)*

Weight/power ratio 2,42 kg/CV (7.16 lbs/kW)

Weight distribution fr/r 42%/58%

Engine

Type V8 – 90°

Displacement 4499 cc (274.5 cu in.)

Maximum power 570 CV (425 kW)** @ 9000 rpm

Maximum torque 540 Nm (398 lbs/ft) @ 6000 rpm

Specific power output 127 CV/l

Compression ratio 12.5:1

Tyres

Front 235/35 ZR20 8.5"

Rear 295/35 ZR20 10.5"

Performance

Maximum speed >325 km/h (>202 mph)

0-100 km/h

Fuel consumption + emissions

Fuel consumption*** 13.7 l/100 km

Emissions*** 320 g CO2/km

Gearbox

Dual-clutch, 7-speed F1

Electronics

E-Diff3, F1-Trac, high-performance ABS

* With forged wheels and Racing seats

** Including 5 CV of ram effect

*** Combined cycle (ECE+EUDC)

Monday, 14 November 2011

Mercury Interview Questions

Q1. What is Software Testing?
Ans. Operation of a system or application under controlled conditions and evaluating the results. The controlled conditions must include both normal and abnormal conditions. It is oriented to detection.

Q2. What is Software Quality Assurance?
Ans. Software QA involves the monitoring and improving the entire software development process, making sure that any agreed-upon standards and procedures are followed. It is oriented to prevention.

Q 3. What are the qualities of a good test engineer?
Ans.

A good test engineer has a test to break attitude.
An ability to take the point of view of the customer
a strong desire for quality
Tactful and diplomatic
Good communication skills
Previous software development experience can be helpful as it provides a deeper understanding of the software development process
Good judgment skills

Q4. What are the qualities of a good QA engineer?
Ans.

The same qualities a good tester
Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization.
In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed.
An ability to find problems as well as to see 'what's missing' is important for inspections and reviews.

Q5. What are the qualities of a good QA or Test manager?
Ans.

Must be familiar with the software development process
able to maintain enthusiasm of their team and promote a positive atmosphere
always looking for preventing problems
able to promote teamwork to increase productivity
able to promote cooperation between software, test, and QA engineers
have the skills needed to promote improvements in QA processes
have the ability to say 'no' to other managers when quality is insufficient or QA processes are not being adhered
have people judgement skills for hiring and keeping skilled personnel
be able to run meetings and keep them focused

Q6. What is the 'software life cycle'?
Ans. The life cycle begins when an application is first conceived and ends when it is no longer in use.

Q7. Tell us about some world famous bugs
Ans. 1. In December of 2007 an error occurred in a new ERP payroll system for a large urban school system. More than one third of employees had received incorrect paychecks that results in overpayments of $53 million. Inadequate testing reportedly contributed to the problems

2. A software error reportedly resulted in overbilling to 11,000 customers of a major telecommunications company in June of 2006. Making the corrections in the bills took a long time.

3. In March of 2002 it was reported that software bugs in Britain's national tax system resulted in more than 100,000 erroneous tax overcharges.

Q8. What are the common problems in the software development process?
Ans.

Poor requirements
Unrealistic schedule
Inadequate testing
A request to pile on new features after development is unnderway.
Miscommunication

Q9. What are the common solutions to software development problems?
Ans.

Solid requirements
Realistic schedules
Adequate testing
stick to initial requirements where feasible
require walkthroughs and inspections when appropriate

Q10. What is a Quality Software?
Ans. Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and / or expectations, and is maintainable.

Q11. What is good code?
Ans. Good code is code that works, is reasonably bug free, and is readable and maintainable.

Q12. What is good design?
Ans. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable. It should also be robust with sufficient error-handling and status logging capability and work correctly when implemented. And, good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements.

Q13. What's the role of documentation in QA?
Ans. QA practices must be documented to enhance their repeatability. There should be a system for easily finding and obtaining information and determining what documentation will have a particular piece of information.

Q14. Which projects may not need independent test staff?
Ans. It depends on the size & nature of the project. Then, it depends on business risks, development methodology, the skills and experience of the developers.

Q15. Why does software have bugs?
Ans.

miscommunication or no communication
software complexity
programming errors
changing requirements
time pressures
poorly documented code
software development tools
egos - people prefer to say things like:
• 'no problem'
• 'piece of cake'
• 'I can whip that out in a few hours'



QC questions

Mercury Quality Centre is a web-based test management tool. It gives you a centralized control over the entire testing life cycle. It gives an easy interface to manage and organize activities like Requirements coverage, Test Case Management, Test Execution Reporting, Defect Management, and Test Automation. All these activities are provided from a single tool, which is web-based and can be accessed from any where. Hence, making the task of the testers and managers easy.

Mercury Quality Centre can be divided into two parts:

- Site Administrator Bin
- Quality Centre Bin

Site Administration Bin: It is the starting point for the usage of Mercury Quality Centre. This part is used for all the administrative activities. Password for site admin is defined during the installation so make sure that you remember the password during installation. From this part of Mercury Quality Centre, we generally do the following activities:

- Creating the projects
- Assigning users to the projects
- Creating specific roles
- Configuring QTP or Winrunner scripts to use from Mercury Quality Centre
- Configuring the mail servers
- Verifying licensing information
- Information about database

Note: If you are using Winrunner, you need to make sure that backward compatibility property of the application to true.

Quality Center Bin: This part of Mercury Quality Centre gives functionality of almost everything that as a tester or test manager you need to do in your day to day activity apart from execution. This is the most common interface used by the customers or users. In this part, we generally do the following activities:

- Creating test plans
- Defining requirements
- Creating test cases
- Creating test labs
- Associating requirements with defects in essence

Mercury Quality Centre is installed as a service in Microsoft windows environment. Before start working on it, make sure that Mercury Quality Centre service is running.

As soon as you access the application, the first screen is a login screen where you need to provide administrator credentials which were used during the installation of Mercury Quality Centre. Once you are logged on to the SABin, you can perform all the administrative tasks mentioned above.

Note: If Mercury Quality Centre is listening to default port, then you can access the application using the following URL:

http://%7Byourmachinename%7D:8080/sabin/SiteAdmin.htm

Define your projects in SABin. Mercury Quality Center provides the role based accessed to the Projects. For example, A Test Manager can create projects and Test Lead can prepare test plans and tester can write the test cases. This role based access makes it very easy to control access to various artifacts of the project and also distribution of responsibility among team members. Following four things can be managed in Mercury Quality Centre:

- Requirements
- Test Plan
- Test Lab
- Defects

Once you have created a project in SABin, Now log on to QCBin by providing your credentials and access the project that you have created. Here, you will notice different tabs for Requirements, TestPlan, TestLab and Defects.

Under Requirements Tab, you can organize the project requirements. You can also create folder hierarchy to represent various features in your project. This can be accomplished by just right-clicking and choosing appropriate options. After creating requirements, move on to next tab Test Plan.

Test Plan Tab will have information about the test cases. These test cases can also be mapped to requirements created in the earlier steps, thus makes foundation for the traceability metrics. Each requirement can be mapped to one or more than one test cases.

After creating new test case you will see in the left hand pane. The right hand pane will have tabs for writing the steps, mapping to requirements, description, expected result etc. Every test case will have steps and for every step you can specify the expected behavior.

The test cases written here, can also be linked to the QTP or Winrunner Scripts. This way, it is providing you better management for the automation and capability of executing automation scripts from Mercury Quality Centre itself. Once you are done with Test Plan preparation, move on to the next tab Test Lab.

To manage test execution for a specific release, you have to create a Test Lab. Test Labs can be created, specific to the release and execution of test cases specific to release can be managed very easily using this concept. In the Test Lab you can identify the set of test cases already written under test plan to include for execution.

If the test cases are already linked to the requirements, then after each test cycle the management will be able to trace what requirements have been tested.

When you choose the option of manual test execution, a window will open up containing the steps to execute. These steps are executed and after every step you can specify whether it is passed or not. Mercury Quality Center also allows parameterized manual test execution, where some of the default parameters like username, password etc. can automatically be read during the manual execution. If you encounter any defects during the failure of any of the steps, it will be automatically logged in to the defect tracking system of Mercury Quality Centre. Once you are done with Test Execution move on to next tab, Defects.

Report generation is one of the most important part of the test management process. Once you are done with planning and execution, its REPORTING time. Mercury Quality Centre provides a very good reporting feature by providing certain pre-defined reports and also capability to create your own reports.

Qtp Interview Questions

1) Which environments are supported by QTP?
QTP supports the following environments
  • Active X
  • Delphi
  • Java
  • .Net
  • Oracle
  • People Soft
  • Power Builder
  • SAP
  • Siebel
  • Stingray
  • Terminal Emulator
  • Visual Basic
  • Visual Age
  • Web
  • Web Services


2) What are the types object Repositories in QTP.
QTP Supports 2 types of Object Repository
1) Shared Object Repository (also called Global)

2) Per-Action Object Repository, (also called Local)

Per-Action Object Repository is used by default. The extension for Per-Action repository is ".mtr" .
Shared Object Repository is preferable while dealing with dynamic objects which are called in multiple tests. The extension is ".tsr"
3) Can we call QTP test from another test using scripting. Suppose there are 4 tests and I want to call these tests in a main script. Is this possible in QTP? 
Yes.  You can call 4 or even more scripts in your tests.For this, first you will need to make the Actions in the corresponding scripts re-usable.Then from the destination script you can make calls to these re-usable actions.
4) What is action split and the purpose of using this in QTP?
Action split is to divide an existing action into two parts.The purpose is to divide actions based on their functionality to improve code re-use.
5) How will you handle Java tree in QTP ?
Foremost you will select Java Add - In and launch QTP. Next step record operations on the Java Tree. If you face an issue while recording, you can select Tools > Object Identification > Java, tree object and make changes in mandatory and assistive properties to enable identification.
Tip: You can base you answer on similar lines for any other object of any environment. For example : If the question is how will check SAP checkbox , You say , first I will select SAP Add in ... and so on.
6) Explain how QTP identifies object ?
QTP identifies any GUI Object based on its corresponding properties.  While recording, QTP will identify and store peculiar properties (as defined in the Object Identification settings) in the object repository of the GUI object . At run-time, QTP will compare the stored property values with the on-screen properties, to uniquely identify the GUI object.
Learn more about Object Identification


7) How many types of recording modes in QTP? Which will be used when ?
QTP supports 3 types of recording modes

1. Normal mode also called Contextual
2. Low-level recording mode
3.Analog mode

Normal Mode: It is the default recording mode and takes full advantage of QTP's Test Object Model. It recognizes objects regardless of their position on -screen. This is the preferred mode of recoding and is used for most of the automation activities.
Low-level recording mode: This mode records the exact x,y co-ordinates of your mouse operations. It is helpful in testing hashmaps. It is useful for recording objects not identified by normal mode of QTP.
Analog mode: This mode records exact mouse and keyboard "movements" you perform in relation to the screen / application window. This mode is useful for the operation such as drawing a picture, recording signature., drag and drop operations.

Learn more about Recording Modes in QTP


8) How will you  call from one action to another action ?
We can call an action in 2 ways
1) Call to copy of Action. - In this ,the Action Object Repository , Script and Datable will be copied to the destination Test Script.
2) Call to Existing Action. - In this,  Object Repository , Script and Datable  will NOT be copied but a call (reference) would be made to the Action in the source script.


9) What are Virtual Objects?
Your application may contain objects that behave like standard objects but are not recognized by QTP. You can define these objects as virtual objects and map them to standard classes, such as a button or a check box. QTP emulates the user's action on the virtual object during the run session. In the test results, the virtual object is displayed as though it is a standard class object.
For example, suppose you want to record a test on a Web page containing a bitmap that the user clicks. The bitmap contains several different hyperlink areas, and each area opens a different destination page. When you record a test, the Web site matches the coordinates of the click on the bitmap and opens the destination page.
To enable QTP to click at the required coordinates during a run session, you can define a virtual object for an area of the bitmap, which includes those coordinates, and map it to the button class. When you run a test, QTP clicks the bitmap in the area defined as a virtual object so that the Web site opens the correct destination page.

10) How to perform Cross platform testing and Cross browser testing using QTP? Can u explain giving some example?
You will need to create separate Actions which take care of different OS and Browsers

Cross Platform Testing:

Using the Built in Environment Variable you can dig up the OS information.
Eg. Platform = Environment("OS"). Then based on the Platform you need to call the actions which you recorded on that particular platform.

Cross Browser Testing:

Using this code  Eg. Browser("Core Values").GetROProperty("version") you can extract the Browser and its correspondin version. Ex: Internet Explorer 6 or Netscape 5. Based on this value you call the actions which are relevant to that browser.


11) What is logical name of the object?
Logical name is a name  given by  QTP while creating an object in the repository to uniquely identify it from other objects in the application. This name would be used by the QTP to map the object name in script with its corresponding description in the object repository. Ex: Browser("Browser").Page("Guru99") Here Guru99 is the logical name of the object.

12) What is descriptive programming?
Typically ,an object and its properties must be recorded in the Object Repository to enable QTP to perform action s on it. 
Using descriptive programming , you do not store the object and its property values in the Object repository but mention the property value pair directly in the script.
The idea behind descriptive programming is not bypass the object repository but help recogonize dynamic objects.

Learn more about Descriptive Programming

13)What are the properties you would use for identifying a browser & page when using descriptive programming ?
You can use the name property
ex: Browser("name:="xxx"").page("name:="xxxx"").....

OR

We can also use the property "micClass".
ex: Browser("micClass:=browser").page("micClass:=page")....

14)Can we record an application running on a remote machine using QTP ?

Yes .you can record remote application provided you are accessing application through the local browser not via remoter like citrix.
If you are still unable to record it is advisable install QTP and application, on the same machine

15) Explain the keyword CreateObject with an example.

Creates and returns a reference to an Automation object
SYNTAX: CreateObject(servername.typename [, location])
Arguments
servername: Required. The name of the application providing the object.
typename :  Required. The type or class of the object to create.
location :  Optional. The name of the network server where the object is to be created.

Example : Set IE = CreateObject("InternetExplorer.Application")

16) Can you switch between Per-Action and Shared Object Repository ? If yes how ?
Yes .We can switch. Go to Test--->Settings--->Resources. Here  you have an option to choose repositories.


17) What is Object Spy ? How to Use it ?
Object Spy helps in determining the run & test time object properties & methods of the application under test.
You can access object spy directly from the toolbar or from the Object Repository Dialog Box.
It is very useful during Descriptive Programming

Learn more about Object Spy


18) When ordinal identifiers alone can make an object unique then why they are not given top priority? Why it is first mandatory and next assistive. Why we cannot go for ordinal identifiers directly?
Consider the following -
a) If two objects are overlapped on each other than location based object recognition will fail.
b) If only index based recognition is used your script will work but script execution time will increase.
Hence mandatory and assistive properties are used.

19) What is the file extension of the code file in QTP?
Code file extension is script.mts

20) Explain in brief about the QTP Automation Object Model.
QTP Automation Object model deals with Automation of QTP itself. Almost all configuration and functionality provided by QTP is represented by QTP's Automation Object Model . Almost all dialog boxes in QTP have a corresponding automation object which can set or retrieved using the corresponding properties or methods in the Automation Object Model.QTP Automation Objects can be used along with standard VB programming elements like iterative loops or conditional statements to help you design a script of choice.

21) What is the use of Text output value in QTP?
Text Output values enable you to capture text appearing on the application under test during run-time.
If parameterized, text output values will capture values appearing in each iteration which would be stored in the run-time data table for further analysis.

22) What is Step Generator?
Step Generator enables use to Add Test Steps in your script. Using step generator you can add steps to your script without actually recording it.


23) How to make QTP understand the difference amongst the  same type of objects .Suppose there are 5 check boxes in a page and I have to choose the 2nd one, how to do that through script?
You can use ordinal identifiers like index along with a little descriptive programming for object recognition.
Watch a video of this example.

24) What is Test Fusion Report ?.
Test Fusion Report , displays all aspects of a test run and is organized in a Tree format.
It gives details of each step executed for all iterations.
It also gives Run-time data table, Screen shots and movie of the test run if opted.
25) How can you handle exceptions in QTP?
In QTP Exceptional handling is done by using
a. Recovery Scenarios. b. Using “On Error” statement
In Recovery scenario you have to define.
1. Triggered Events.
2. Recovery steps.
3. Post Recovery Test-Run.
At Script Level you can use the On Error Resume Next and On Error Go to 0 statement.





26) What are the types of environment variables in QTP ?
Environment variables in QTP are of three types:
1) Built-in (Read only)
2) User-defined Internal (Read only)
3) User-defined External (Read/Write)

You Set the Environment Variable  using the following syntax 
Environment.Value( "name") = "Guru99"
You can Retrieve the Environment Variable using following syntax
Environment.Value("name") -- This will retrun name as Guru99

Environment.Value("OS")  -- This will return your system OS



27) What is the Difference between Bitmap Check point & Image Check point?
Bitmap
checkpoint does a pixel to pixel comparison of an image or part of an image.
Image checkpoint does do a pixel to pixel comparison but instead compare image properties like alt text , destination url etc.

28) What is the difference between functions and actions in QTP?
Actions have their own Object Repository & Data Table. Actions help make your Test modular and increase reuse. Example: You can divide your script into Actions based on functionality like Login, Logout etc.
Functions is a VB Script programming concept and do not have their own Object Repository or Data Table. Functions help in re-use of your code. Ex:  You can create a Function in your script to concatenate two strings.

29) What is keyword view and Expert view in QTP? -
Keyword View is an icon based view which shows test steps in tabular format. It also automatically generates documentation for the test steps.
Expert View gives the corresponding VB Script statement for every test step in the Keyword view.

30)  Explain QTP Testing process? -
Quick Test testing process consists of 6 main phases:
1)  Create your test plan - This is preparatory phase where you identify the exact test steps, test data and expected results for you automated test. You also identify the environment and system configurations required to create and run your QTP Tests.
2) Recording a session on your application - During this phase , you will execute test steps one by one on your AUT ,and QTP will automatically record corresponding VB script statements for each step performed.
3) Enhancing your test - In this stage you will insert checkpoints , output values , parameterization , programming logic like if…else loops to enhance the logic of your test script.
4) Replay & Debug - After enhancements you will replay the script to check whether its working properly and debug if necessary.
5) Run your Tests - In this phase you will perform the actual execution of your Test Script.
6) Analyzing the test results - Once test run is complete, you will analyze the results in the Test Fusion report generated.
7) Reporting defects - Any incidents identified needs to be reported. If you are using Quality Center , defects can be automatically raised for failed tests in QTP.

31) What are the different types of Test Automation Frameworks ?
The types of Automation Frameworks are -
1) Linear Scripting - Record & Playback
2) The Test Library Architecture Framework.
3)The Data-Driven Testing Framework.
4)The Keyword-Driven or Table-Driven Testing Framework.


Learn more about Test Automation Frameworks.



32) How will you check a web application for broken links using QTP?
You can use the Page Checkpoint which gives a count of valid/invalid links on a page.

33) What is a Run-Time Data Table? Where can I find and view this table?
Data like parameterized output , checkpoint values , output values  are stored in the Run-time Table. It is an xls file which is stored in the Test Results Folder.  It can also be accessed in the Test Fusion Report.


34) What is the difference between check point and output value.

Check point is a verification point that compares a current value for a specified property with the expected value for that property. Based on this comparison, it will generate a PASS or FAIL status. 

An output value is a value captured during the test run and can be stored in a specified location like the  Datable or even a variable. Unlike Checkpoints, no PASS/FAIL status is generated.


34) How would you connect to database using vbscript ?
To connect to the database you must know
a) connection string of your server
b) username
c) password
d) DNS name
You can code the database connectivity command directly or you can use the SQL Query tool provided by QTP.

35) What is QTP batch testing tool?
 You can use the Batch testing tool to run multiple scripts. Once the scripts are added in the tool , it  will automatically open the scripts and start executing them one after the other.

36) What are the drawbacks of QTP?
As of QTP version 10
1) Huge Tests in QTP consume lots of memory and increase CPU utilization.
2) Since QTP stores results in HTML file (and not txt) the result folder sometimes becomes big.

37) What is an Optional Step ?
A step when declared optional is not mandatory to be executed. If the corresponding GUI object is present, QTP performs the operation on it. If the GUI object is not present, QTP bypasses the optional step and proceeds to execute the next step.


38) What  is Reporter.ReportEvent ?
Reporter.Reportvent is standard method provided by QTP to send custom messages to the test results window.
Syntax
Reporter.ReportEvent EventStatus, ReportStepName, Details [, ImageFilePath]
where     
EventStatus = 0 or micPass
                    1 or micFail
                    2 or micDone
                    3 or micWarning
 Results can assume any status like Pass , Fail , Warning etc. You can also send screenshot to the test results window.

39) How will you  declare a variable in QTP ?
You declare using a DIM keyword. You assign value to the variable using the SET keyword.
Ex.
Dim temp 'Will declare the temp variable
Set  temp = 20 ' Will assign a value 20 to temp.

39) What is GetRoProperty ?
 GetRoProperty is a standard method provided by QTP to fetch property values of a run -time object.

40) What is smart Identification?
Typically, if even one of the on-screen object property does not match the recorded object property. The test fails.
In smart identification, QTP does not give an error if the property values do not match, but uses Base filter and Optional Filter properties to uniquely identify an object. In Smart identification, if a property value does not match the script does not fail but it proceeds ahead to compare the next property. Smart identification can be enabled in Object Identification Dialog box.
Learn more about SMART Identification

41) How would you export a Script from one PC to another in QTP ?
We can make use of the "Generate Script" function available in Object Identification, Test Settings and Tools/Options tab to create a zip of the script at the source computer. These zip files then can be imported into QTP at the destination computer.


42) Can launch two instances of QTP on the same machine ?
No. You can work with only single instance of QTP on the same machine. But QTP itself can work on multiple instances of the Application Under Test (AUT). Ex:  QTP can handle multiple IE browser windows.

43) Give the syntax to import/export xls into QTP.
DataTable.ImportSheet "..\..\TestData\Input.xls",1,dtGlobalSheet DataTable.ExportSheet "..\..\Results\Output.xls","Global"

44) What is SetToProperty ?
SetToProperty changes property of an object stored in the Object Repository. However these changes are not permanent.
45) What is the standard timing delay for web based application in QTP ?
The standard delay is 60 seconds. This is can be changed in Test Settigns.


46) What is the Action Conversion Tool ?
It is an in-built tool provided by QTP to convert Actions into Business Process Components.

47) What is the extension for a function library ?
The extension is  '.QFL'

48) If the Global Data sheet contains no data and the Local Datasheet contains two rows of data, how many times will the test iterate?
The test will iterate only once - global iteration.

49)  What factors affect bitmap checkpoints ?
Bitmap checkpoints are affected by screen resolution and image size.

50)  What is Accessibility Checkpoint?
World Wide Web Consortium (W3C) came up with some instructions and guidelines for Web-based technology and information systems to make it easy for the disabled to access the web. For example the standards make it mandatory to have an 'alt text' for an image. So a blind person who is accessing the website, will use text - to -speech converters and atleast understand what the image is about if not see it. All these standards are checked by Accessibility Checkpoints.

1. How Does Run time data (Parameterization) is handled in QTP?
A). You can then enter test data into the Data Table, an integrated Spreadsheet with the full functionality of Excel, to manipulate data Sets and create multiple test iterations, without programming, to Expand test case coverage. Data can be typed in or imported from Databases, spreadsheets, or text files.

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

3) Explain about the Test Fusion Report of QTP?
A) Once a tester has run a test, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team.

4) To which environments does a QTP support?
A) QuickTest Professional supports functional testing of all enterprise environments, including Windows, Web, NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.

5) What is QTP?
A) QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework applications.

6) Explain QTP testing process?
A) The QuickTest testing process consists of 6 main phases:

1. Create your test plan: Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.

2. Recording a session on your application: As you navigate through your application, QuickTest graphically displays each step you perform in the form of a collapsible icon-based test tree . A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.

3. Enhancing your test: Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly.

NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process.

Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data. Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.

4. Debugging your test: If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.

5. Running your test on a new version of your application: You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.

6. Analyzing the test results: You examine the test results to pinpoint defects in your application.

7. Reporting defects: As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

7) Explain the QTP Tool interface.

A) It contains the following key elements:

- Title bar, displaying the name of the currently open test

- Menu bar, displaying menus of QuickTest commands

- File toolbar, containing buttons to assist you in managing tests

- Test toolbar, containing buttons used while creating and maintaining tests

- Debug toolbar, containing buttons used while debugging tests.

Note: The Debug toolbar is not displayed when you open QuickTest for the first time. You can display the Debug toolbar by choosing View > Toolbars > Debug.

- Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow.

Note: The Action toolbar is not displayed when you open QuickTest for the first time. You can display the Action toolbar by choosing View > Toolbars > Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically.

- Test pane, containing two tabs to view your test-the Tree View and the Expert View Test Details pane, containing the Active Screen.

- Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.)

- Status bar, displaying the status of the test.

8) How QTP recognizes Objects in AUT?
A) QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object.

Each line in the QuickTest script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.

9) What are the types of Object Repository’s in QTP?
A) QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test.

The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.

10) Explain the check points in QTP?

A). A checkpoint verifies that expected information is displayed in a Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.

- A page checkpoint checks the characteristics of a Application.
- A text checkpoint checks that a text string is displayed in the appropriate place on a Application.
- An object checkpoint (Standard) checks the values of an object on a Application.
- An image checkpoint checks the values of an image on a Application.
- A table checkpoint checks information within a table on a Application.
- An Accessibility checkpoint checks the web page for Section 508 compliance.
- An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
- Adatabase checkpoint checks the contents of databases accessed by your web site.

11) In how many ways we can add check points to an application using QTP. A) We can add checkpoints while recording the application or we can add after recording is completed using Active screen

(Note : To perform the second one The Active screen must be enabled while recording).

12) How does QTP identifies the object in the application?
A) QTP identifies the object in the application by Logical Name and Class.

13) If an application name is changes frequently i.e while recording it has name "Window1" and then while running its "Windows2" in this case how does QTP handles?

A) QTP handles those situations using "Regular Expressions".

14) What is Parameterizing Tests?
A) When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.

15) What is test object model in QTP?
A) The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that QuickTest can record for it.

A test object is an object that QuickTest creates in the test or component to represent the actual object in your application. QuickTest stores information about the object that will help it identify and check the object during the run session.
A run-time object is the actual object in your Web site or application on which methods are performed during the run session.

When you perform an operation on your application while recording, QuickTest identifies the test object class that represents the object on which you performed the operation and creates the appropriate test object reads the current value of the object's properties in your application and stores the list of properties and values with the test object chooses a unique name for the object, generally using the value of one of its prominent properties records the operation that you performed on the object using the appropriate QuickTest test object method. For example, suppose you click on a Find button with the following HTML source code:

<INPUT TYPE="submit" NAME="Find" VALUE="Find">

QuickTest identifies the object that you clicked as a WebButton test object. It creates a WebButton object with the name Find, and records the properties and values for the Find WebButton. It also records that you performed a Click method on the WebButton. QuickTest displays your step like this:

Browser("Mercury Interactive").Page("Mercury Interactive").
WebButton("Find").Click

16) What is Object Spy in QTP?
A) Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object's hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.

17) What is the Diff between Image check-point and Bit map Check point?
A) Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map.

Using the bitmap checkpoint, you can check that the map zooms in correctly. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins is loaded). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

18) How many ways we can parameterize data in QTP?

A) There are four types of parameters:

- Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test.

- Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, QuickTest uses a different value from the Data Table.

- Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that QuickTest generates for you based on conditions and options you choose.

- Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have QuickTest generate a random number and insert it in a number of tickets edit field.

19. How do u do batch testing in WR & is it possible to do in QTP, if so explain?
Ans: Batch Testing in WR is nothing but running the whole test set by selecting "Run Testset" from the "Execution Grid". The same is possible with QTP also. If our test cases are automated then by selecting "Run Testset" all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in "Waiting" mode.

20. What does it mean when a check point is in red color? what do u do?
Ans : A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.

21. What do you call the window test director - testlab?
Ans : "Execution Grid". It is place from where we Run all Manual / Automated Scripts.

22. How does u create new test sets in TD?

Ans :

- Login to TD.
- Click on "Test Lab" tab.
- Select the Desired folder under which we need to Create the Test Set. (Test Sets can be grouped as per module.)
- Click on "New Test Set or Ctrl+N" Icon to create a Test Set.

23. How do u do batch testing in WR & is it possible to do in QTP, if so explain?
Ans : You can use Test Batch Runner to run several tests in succession. The results for each test are stored in their default location.

Using Test Batch Runner, you can set up a list of tests and save the list as an .mtb file, so that you can easily run the same batch of tests again, at another time. You can also choose to include or exclude a test in your batch list from running during a batch run.

24. How to Import data from a ".xls" file to Data table during Runtime.

Ans :

- Datatable.Import "...XLS file name..."
- DataTable.ImportSheet(FileName, SheetSource, SheetDest)
- DataTable.ImportSheet "C:\name.xls" ,1 ,"name"

25. How to export data present in Datatable to an ".xls" file?
Ans : DataTable.Export "....xls file name..."

26. Syntax for how to call one script from another and Syntax to call one "Action" in another?
Ans: RunAction ActionName, [IterationMode , IterationRange , Parameters]

Here the actions become reusable on making this call to any Action.
IterationRange String Not always required. Indicates the rows for which action iterations will be performed. Valid only when the IterationMode is rngIterations. Enter the row range (i.e. "1-7"), or enter rngAll to run iterations on all rows.
If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the value of the ExitAction's RetVal argument.

27. How to export QTP results to an ".xls" file?
Ans : By default it creates an "XML" file and displays the results.

28. Differences between QTP & Winrunner?
Ans :

- QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.
- QTP supports ".NET" application Automation not available in Winrunner.
- QTP has "Active Screen" support which captures the application, not available in WR.
- QTP has "Data Table" to store script values , variables which WR does not have.
Using a "point and click" capability you can easily interface with objects, their definitions and create checkpoints after having recorded a script without having to navigate back to that location in your application like you have to with WinRunner. This greatly speeds up script development.

29. How to add a runtime parameter to a datasheet?
Ans: By using LocalSheet property. The following example uses the LocalSheet property to return the local sheet of the run-time Data Table in order to add a parameter (column) to it:

MyParam=DataTable.LocalSheet.AddParameter("Time", "5:45")

30. What scripting language is QTP of?
Ans : VB Script.

31. Analyzing the Checkpoint results
Standard Checkpoint: By adding standard checkpoints to your tests or components, you can compare the expected values of object properties to the object's current values during a run session. If the results do not match, the checkpoint fails.

32. Table and DB Checkpoints: By adding table checkpoints to your tests or components, you can check that a specified value is displayed in a cell in a table on your application. By adding database checkpoints to your tests or components, you can check the contents of databases accessed by your application.

The results displayed for table and database checkpoints are similar. When you run your test or component, QuickTest compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails.

You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object. To add a table checkpoint, you use the Checkpoint Properties dialog box.

Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments.

You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query.

Database checkpoints are supported for all environments supported by QuickTest, by default, as well as for a variety of external add-in environments.

There are two ways to define a database query:

- Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office.
- Manually define an SQL statement.

The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint.

33. Checking Bitmaps:
A.) You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk space.

When you run the test or component, QuickTest compares the object or selected area of the object currently displayed on the Web page or application with the bitmap stored when the test or component was recorded. If there are differences, QuickTest captures a bitmap of the actual object and displays it with the expected bitmap in the details portion of the Test Results window. By comparing the two bitmaps (expected and actual), you can identify the nature of the discrepancy.

For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.

You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins is loaded).

Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

34. Text/Text Area Checkpoint: In the Text/Text Area Checkpoint Properties dialog box, you can specify the text to be checked as well as which text is displayed before and after the checked text. These configuration options are particularly helpful when the text string you want to check appears several times or when it could change in a predictable way during run sessions.

Note: In Windows-based environments, if there is more than one line of text selected, the Checkpoint Summary pane displays [complex value] instead of the selected text string. You can then click Configure to view and manipulate the actual selected text for the checkpoint.

QTP automatically displays the Checked Text in red and the text before and after the Checked Text in blue. For text area checkpoints, only the text string captured from the defined area is displayed (Text Before and Text After are not displayed).

To designate parts of the captured string as Checked Text and other parts as Text Before and Text After, click the Configure button. The Configure Text Selection dialog box opens.

35. Checking XML: XML (Extensible Markup Language) is a meta-markup language for text documents that is endorsed as a standard by the W3C. XML makes the complex data structures portable between different computer environments/operating systems and programming languages, facilitating the sharing of data.

XML files contain text with simple tags that describe the data within an XML document. These tags describe the data content, but not the presentation of the data. Applications that display an XML document or file use either Cascading Style Sheets (CSS) or XSL Formatting Objects (XSL-FO) to present the data.

You can verify the data content of XML files by inserting XML checkpoints. A few common uses of XML checkpoints are described below:

- An XML file can be a static data file that is accessed in order to retrieve commonly used data for which a quick response time is needed—for example, country names, zip codes, or area codes. Although this data can change over time, it is normally quite static. You can use an XML file checkpoint to validate that the data has not changed from one application release to another.

- An XML file can consist of elements with attributes and values (character data). There is a parent and child relationship between the elements, and elements can have attributes associated with them. If any part of this structure (including data) changes, your application's ability to process the XML file may be affected. Using an XML checkpoint, you can check the content of an element to make sure that its tags, attributes, and values have not changed.

- XML files are often an intermediary that retrieves dynamically changing data from one system. The data is then accessed by another system using Document Type Definitions (DTD), enabling the accessing system to read and display the information in the file. You can use an XML checkpoint and parameterize the captured data values in order to check an XML document or file whose data changes in a predictable way.

- XML documents and files often need a well-defined structure in order to be portable across platforms and development systems. One way to accomplish this is by developing an XML schema, which describes the structure of the XML elements and data types. You can use schema validation to check that each item of content in an XML file adheres to the schema description of the element in which the content is to be placed.

36. Object Repositories types, which & when to use?
A.) To choose the default object repository mode and the appropriate object repository mode for each test, you need to understand the differences between the two modes. In general, the object repository per-action mode is easiest to use when you are creating simple record and run tests, especially under the following conditions:

- You have only one, or very few, tests that correspond to a given application, interface, or set of objects.

- You do not expect to frequently modify test object properties.

- You generally create single-action tests.

Conversely, the shared object repository mode is generally the preferred mode when:

- You have several tests that test elements of the same application, interface, or set of objects.

- You expect the object properties in your application to change from time to time and/or you regularly need to update or modify test object properties.

- You often work with multi-action tests and regularly use the Insert Copy of Action and Insert Call to Action options.

37. Can we Script any test case with out having Object repository? or Using Object Repository is a must?
Ans: No. U can script with out Object repository by knowing the Window Handlers, spying and recognizing the objects logical names and properties available.

38. How to execute a WinRunner Script in QTP?
Ans :

(a) TSLTest.RunTest TestPath, TestSet [, Parameters ] --> Used in QTP 6.0 used for backward compatibility

Parameters: The test set within Quality Center , in which test runs are stored. Note that this argument is relevant only when working with a test in a Quality Center project. When the test is not saved in Quality Center , this parameter is ignored.
e.g : TSLTest.RunTest "D:\test1", ""

(b) TSLTest.RunTestEx TestPath, RunMinimized, CloseApp [, Parameters ]
TSLTest.RunTestEx "C:\WinRunner\Tests\basic_flight", TRUE, FALSE, "MyValue"
CloseApp : Indicates whether to close the WinRunner application when the WinRunner test run ends.
Parameters : Up to 15 WinRunner function argument

39. How to handle Run-time errors?
Ans: On Error Resume Next : causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. This allows execution to continue despite a run-time error. You can then build the error-handling routine inline within the procedure. Using "Err" object msgbox "Error no: " & " " & Err.Number & " " & Err.description & " " & Err.Source & Err.HelpContext

40. How to change the run-time value of a property for an object?
Ans : SetTOProperty changes the property values used to identify an object during the test run. Only properties that are included in the test object description can be set.

41. How to retrieve the property of an object?
Ans : using "GetRoProperty".

42. How to open any application during Scripting?
Ans : SystemUtil, object used to open and close applications and processes during a run session. A SystemUtil.Run statement is automatically added to your test when you run an application from the Start menu or the Run dialog box while recording a test
E.g : SystemUtil.Run "Notepad.exe"
SystemUtil.CloseDescendentProcesses (Closes all the processes opened by QTP)

43. Types of properties that Quick Test learns while recording?

Ans : (a) Mandatory (b) Assistive .

In addition to recording the mandatory and assistive properties specified in the Object Identification dialog box, QuickTest can also record a backup ordinal identifier for each test object. The ordinal identifier assigns the object a numerical value that indicates its order relative to other objects with an otherwise identical description (objects that have the same values for all properties specified in the mandatory and assistive property lists). This ordered value enables QuickTest to create a unique description when the mandatory and assistive properties are not sufficient to do so.

44. What is the extension of script and object repository files?
Ans : Object Repository : .tsr , Script : .mts, Excel : Default.xls

45. How to supress warnings from the "Test results page"?
Ans : From the Test results Viewer "Tools > Filters > Warnings"...must be "Unchecked".

46. When we try to use test run option "Run from Step", the browser is not launching automatically why?

Ans : This is default behaviour.

47. How to "Turn Off" QTP results after running a Script?
Ans : Goto "Tools > Options > Run Tab" and Deselect "View results when run session ends". But this supresses only the result window, but a og will be created and can viewed manulaly which cannot be restricted from getting created.

48. How to verify the Cursor focus of a certain field?
Ans : Use "focus" property of "GetRoProperty" method"

49. How to make arguments optional in a function?
Ans : this is not possible as default VBS doesn't support this. Instead you can pass a blank scring and have a default value if arguments r not required.

50. How to covert a String to an integer?
Ans : CInt()---> a conversion function available.

51. Inserting a Call to Action is not importing all columns in Datatable of globalsheet. Why?
Ans : Inserting a call to action will only Import the columns of the Action called

52. How to get "FontSize" of a "WebEdit"?

53. Does QTP is "Unicode" compatible?

54. How to get "FontSize" of a "WebEdit"?

55. Is there anyway to automatically update the Datasource name in Database Checkpoints object when we migrate tests to a new release?

56. Any limitation to XML Checkpoints?

57. What do you to script when objects are removed from application?

58. How to create a Runtime property for an object?

59. How to attach a file to TD?


1) What are the Features & Benefits of Quick Test Pro ?
Ans. Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving capability. Identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a single step with Auto-documentation technology. Enables thorough validation of applications through a full complement of checkpoints.
2) How to handle the exceptions using recovery scenario manager in QTP?
Ans. There are 4 trigger events during which a recovery scenario should be activated. A pop up window appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions.You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has three steps:
  • Triggered Events
  • Recovery steps
  • Post Recovery Test-Run
3) What is the use of Text output value in QTP?
Ans. Output values enable to view the values that the application talks during run time. When parameterized, the values change for each iteration. Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.
4) How to use the Object spy in QTP 8.0 version?
Ans. There are two ways to Spy the objects in QTP:
  • Thru file toolbar, In the File Toolbar click on the last toolbar button (an icon showing a person with hat).
  • True Object repository Dialog
In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and release the Ctrl button.
5) Explain the concept of object repository & how QTP recognizes objects?
Ans. Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code.
6) What are the properties you would use for identifying a browser & page when using descriptive programming?


Ans. Name would be another property apart from title that we can use.
7) Give me an example where you have used a COM interface in your QTP project?
Ans. COM interface appears in the scenario of front end and back end. for eg: if you r using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation.


8) Explain in brief about the QTP Automation Object Model.
Ans. Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program.