QTP Interview questions

1 When a procedure is created in the Function Library editor, what is the extension on the file? 

A. .INI B. .TXT C. .QFL D. .VBS

 2. What are the categories in the Step Generator?

 A. Object, Operation, Value B. Library, Built-in, Local Script C. Operation, Arguments, Return Value D. Test Objects, Utility Objects, Functions

 3. In Test Settings ->Run the Data Table iteration options are for which data sheet?  A. Local B. Global C. Run-time Data Table D. Design-time Data Table

 4. What can you use to handle unpredictable testing exceptions? 

A. A Do Loop B. Recovery Scenario C. IFHEN statement D. Selectase statement 

 5. In which command can you associate a function library to a test? 

A. Run Options B. Test Settings   C. View Options D. Function Definition Generator 

 6. Where do you set the action iterations for a specified action? 

A. Action Settings B. Action Properties C. Action Run Settings D. Action Call Properties

 7. Where do you mark an action as reusable? 

A. Action Settings B. Action Properties C. Action Run Settings D. Action Call Properties

 8. After running a test that contains both input and output parameters, where can the results of an output parameter be found? 

A. Local DataSheet B. Global DataSheet C. Run-time Data Table D. Design-time Data Table

 9 If you have a Virtual Object Collection stored on your machine, and you don't want to use it, what must you do? 

A. Disable Virtual Objects in Test Settings B. Remove the Collection from your machine C. Disable Virtual Objects in General Options D. Remove the Collections from the Resources list

 10 Which method for the DataTable utility object will allow you to retrieve information from the Data Table during a test run? 

A. Value B. Import C. GetCell D. GetValue

 11 What does the source property of a database checkpoint object represent? 

A. The SQL query B. The identification number of the database C. The number of rows returned from the query D. The connectionstring used to connect to the database

 12. What is created, by default, with each new action?

 A. Local Data Sheet, Global Data Sheet, Folder B. Local Object Repository, Local Data Sheet, Folder C. Global Data Sheet, Local Object Repository, Folder D. Local Data Sheet, Global Data Sheet, Local Object Repository

 13. What are the available environment variable type(s)? 

A. Built-in B. User-defined C. User-function D. Built-in, User-defined E. Built-in, User-function

 14. If the Global Data sheet contains no data and the Local Datasheet contains two rows of data, how many times will the test iterate?

   A. 1 B. 2 C. 3 D. 5  Answer: A

 15. What is the first thing that must be defined in a Recovery Scenario? 

A. Trigger B. Recovery Operation C. Recovery Scenario Name D. The Function used in the scenario

 16. What are bitmap checkpoints sensitive to? 

A. Image size and object type B. Object type and image type C. Screen resolution and object type D. Screen resolution and image size

7. QUESTION 17 If the Local Data sheet contains two rows of data, how many times will the action iterate, by default? 

A. 1 B. 2 C. 3 D. 5

 18. How do you close the database session after examining the results of an SQL query? 

A. Call the ADO.Close function B. Use the close method for the RecordSet object C. Set the RecordSet and Connection objects equal to Nothing D. Use the close method for the RecordSet and Connection objects

 19. What are the available trigger event types? 

A. Pop-up window, object state, VBScript event B. Object State, VBScript event, Application crash C. Pop-up window, object state, test run error, QTP crash D. Pop-up window, object state, test run error, application crash

 20. What is the keyword used to define how the counter variable in a or lext loop increments?  

A. ++ B. Next C. Skip D. Step

 21. What are the two most commonly used ADO objects? 

A. Fields B. Execute C. Connection, RecordSet D. Open, ConnectionString 

22. How do you declare a constant? 

A. Dim statement B. Con statement C. Const statement D. Option Explicit statement

 23. What method is used to retrieve the number of columns in the query results? 

  A. Fields.Count B. Fields.Item(EOF) C. Fields.Count(BOF) D. Fields.Count.Value

 24. To bypass the Object Repository you can: 

A. Turn the Object Repository off B. Use a programmatic description C. Delete all objects in all repositories D. Add the object to the Object Repository Manager

 25. What does the ChildObjects method return? 

A. A Collection object B. A string true/false C. A Boolean TRUE/FALSE D. The number of objects matching the ChildObject description

 QUESTION 26 What object is used to read information from a text file?  A. Read B. ReadLine C. TextStream D. File System E. Open Text File  Answer: C

 27. If you are typing in Expert View and you type an object followed by a dot, what does QuickTest display? 

A. Nothing B. The arguments for that object C. The methods and properties for that object D. The child objects and methods for that object

 28. By default, how does QuickTest pass arguments to the procedure? 

A. ByVal B. ByRef C. ByArg D. ByRes

 29. What object is used to send information to test results at the completion of the test run? 

A. Result B. Reporter C. ReportEvent D. ResultReport

 30. If a procedure is defined in a test script, that procedure is accessible to which tests/scripts? 

A. Only to other procedures B. It is not usable to any test scripts C. The test script in which it is defined D. Using the Step Generator, it is available to any test script

 31. When does a Do loop statement evaluate for continuation? 

A. At the end of the loop B. At the start of the loop C. At the start or the end of the loop D. This loop uses a counter variable

 32. How can you retrieve the number of items in the list for a WebList object? 

  A. GetList B. GetItem C. GetItemsCount D. GetROProperty

 33. What is the difference between a subroutine and a function? 

A. A subroutine can call itself; a function cannot B. A function returns a value; a subroutine cannot C. A function can accept arguments; a subroutine cannot. D. A subroutine can call other procedures; a function cannot.

 34. What method is used to send a run-time Data sheet to an Excel file? 

A. Send B. Export C. SendSheet D. Exportsheet

 35. What looping statements are available in QuickTest? 

A. Whileend, Doloop, Ifhen B. Switchfase, Ifhen, Fortext C. Fortext, Whileend, Doloop D. Fortext, Doloop, Switchase

 36. What does the GetTOProperty method do? 

A. Retrieves the value of a property from a test object B. Retrieves the available properties from a test object C. Retrieves the value of a property from a run-time object D. Retrieves the available properties from a run-time object

37. To use low-level recording, what must you do first? 

A. Start a new test B. Be in the KeyWord view C. Be recording in Normal mode D. Click Low Level Recording under the Automation Menu

38. What is the correct set of add-ins installed automatically with QuickTest 9.2? 

A. NET, Web, Java B. Web, SAP, Visual Basic C. Active X, Visual Basic, Web D. Active X, TE, Web Services

 39. What information can be seen in the information pane? 

A. Syntax errors B. The test name and author C. The QTP license information D. The machine id and operating system

 40. What does a breakpoint do? 

A. Stops test execution at the specified step, after executing that step B. Stops test execution at the specified step, before executing that step C. Pauses test execution at the specified step, after executing that step D. Pauses test execution at the specified step, before executing that step

 41. Which of the following is an example of a missing resource? 

A. An object B. Run Results  C. A Regular Action D. An External

42. What are the available step commands in QuickTest? 

A. Step, Step Into, Step Out B. Step Into, Step Over, Step Out C. Step Test, Step Action, Step Function D. Run from Step, Debug from Step, Run from

 43. When a test is run in update mode, what is updated? 

A. The test results B. The object descriptions C. The action names in the test D. The logical names in the test

 44. What are the phases in the QuickTest workflow? 

A. Plan, Record, Enhance, Run B. Prepare, Record, Verify, Run C. Plan, Create, Verify & Enhance D. Prepare, Create, Verify & Enhance, Integrate

 45. Why is low-level recording mode useful? 

A. It records exact keyboard operations on an object. B. It records exact coordinates of all mouse movements. C. It uses the object repository to determine what methods can be used.

 46. What are test object properties?

A. Those properties as defined in a description object. B. Those properties as defined in Object Identification C. Those properties displayed by an object at run-time D. Those properties used in the Object Repository for object identification 

 47. What is the function of the Object Repository Manager? 

A. Assign variable names to test objects B. View/make/modify a Local Object Repository C. View/make/modify a Shared Object Repository D. Define new test objects using programmatic descriptions

 48. Where are virtual object collections stored? 

A. In a Function Library B. In the local Object Repository C. In the Object Repository Manager D. Dat folder inside of the QTP installation directory

 49. In the Object Identification dialog box, which properties can be viewed? 

A. The base filter and optional properties B. The mandatory and optional properties C. The base filter and assistive properties D. The mandatory and assistive properties

 50. Where do you turn Smart Identification IN? 

A. The Object Repository B. The Test Settings dialog C. The General Options dialog D. The Object Identification dialog

 51. How do you know if Smart Identification has been used in a test? 

A. The Smart Identification icon appears in the test results B. The test results will show a run error, causing a test failure C. The properties used by the object repository will be changed D. The Object Repository will show the Smart Identification icon

 52. What options are available to filter objects in the Target Object Repository pane when merging object repositories? 

A. Show all objects or Show only objects with conflicting object types B. Show all objects or Show only objects with conflicting descriptions C. Show only objects with conflicting logical names or Show only objects with conflicting object types D. Show only objects with conflicting logical names or Show only objects with conflicting descriptions

 QUESTION 53 What is the default ordinal identifier?  A. The location B. The object id C. The nativeclass D. The index number  Answer: A

 54. Which statement is used to associate a procedure with a test object class? 

A. RegisterFunction B. RegisterUserProc C. RegisterUserFunc D. RegisterProcedure

 55. What must you do before a shared object repository can be edited? 

A. Enable Editing B. Add a new object C. Open the object repository D. Open an action that uses that shared object repository

 56. Where do you configure an action to use a shared object repository? 

A. Test Settings B. Action Settings C. Action Call Properties D. Associate Repositories

 57. You should use local object repositories when you: 

A. Work with single-action tests B. Work with multiple-action tests C. Create multiple tests for a single application D. Expect the test object properties to change frequently

 58. Where can you merge two shared object repositories? 

A. The Object Repository B. The Object Repository Manager C. The Associate Object Repositories Tool D. You can only merge local object repositories

HP UFT 11.5 tool new features

1. HP UFT Overview

The latest version of HP-QTP that is going to hit the market will be known as HP Unified Functional Testing(UFT) 11.5 .

QuickTest Pro (QTP) (GUI Testing Feature)+ Service Test (ST) (API Testing Feature) = Unified Functional Testing (UFT)

This is going to be a major change on how we see QTP. Going forward, QTP and Service Test will be a part of UFT 11.5 software. Acc. to HP, this has been done to serve end to end testing needs. QTP(GUI testing tool) and Service Test(API testing tool) will be available from a single interface, so you need not download two separate tools from now on.

2. Newly added Action features in UFT

• Separate action flows
• Individual data sources
• Independent input/output parameters

3. Insight Recording

HP UFT Insight breaks down barriers with innovative image-based object recognition, which allows the testing software to recognize and record any application, irrespective of the tool used to build it.
With Image-based object identification you can now learn an object’s (or images) different states and convert that into a recognizable object within the object library.

4. Supports Mobile Testing

Realizing the ‘explosive’ growth of mobile (smart-phones + tablets) platform, HP is putting a lot of focus on this new age tech. UFT 11.5 will provide a better support for mobile testing. With the help of HP UFT Mobile, HP claims that you will be able to create mobile platform agnostic scripts, hence a script created for iOS would be expected to work for Android. The mobile application testing solution will support emulators as well as real devices. The real devices can be sourced from the public cloud of shared real devices and/or private cloud of dedicated real devices.

5. ALM Data for UFT

ALM’s Data Awareness feature enables us to

• Save multiple relevant sets of data in our ALM project
• To run A Test with different data configurations, enabling more realistic and data-drive tests of our application

6. API Testing

This is really great feature in this UFT 11.5 tool. where we can test APIs

7. Enhanced Bitmap checkpoint

Validate an image by comparing it to an existing bitmap

8. BPT (Business Process Testing ) with UFT

Now with UFT we can do Business Process Testing without integrating with HP ALM/QC.

9. Enhanced scripting feature with Dot Object

There is a new feature added in Dot Object. We can Set/Get values with child Dot Object methods

10. File content checkpoint

Before UFT 11.5 we used face lot of difficulties to read data from different external files. Now with File content checkpoint we can read the data from different files ex: PDF,HTML, RFT, txt, doc, etc: easily.

11. Loading Function Libraries from HP ALM with LoadFunctionLibrary Method

We can load function library files which are stored in HP ALM during run time.

12. New way to Describe object in UFT

Please see below screen shot for the new way to describe object in UFT.

13. Array Checkpoint

Array checkpoint gives 3 different options to verify the content in array.

• Fixed
• Contains
• All

14. Update in WSDL

If there is any change in WSDL file, we no need to create a new test for that now. UFT has option to update services directly and map arguments.

15. Multiple script Debugging

This was a much needed and requested feature. You will now be able to debug two or more scripts at the same time from within UFT’s IDE.

On top of QTP current debugging capabilities which are limited, but Using this new feature of UFT 11.5 We can able to debug the two or more automation scripts at same time using the UFT 11.5 IDE.

Following panes are greatly added to the HP UFT list of debug features:

The following panes have been added and enhanced:

• Call Stack – allows you to view info about the methods and functions that are currently in the call stack.
• Loaded Modules – for API tests, this pane allows you to view info on .dlls that are loaded and executed in API test runs.
• Threads – For API tests–allows you to view info about threads currently running as part of the run session.
• Local Variables Pane – allows you to view all the current values and types of variables in their current context.
• Console Pane – when debugging a script, this pane allows you to run lines of VBScript (for GUI tests) and C# code (for API tests) in your suspended run session.
• Watch – when debugging, this pane allows you to view the current values ad types of selected variables, properties, and VBScript of C# expressions in a test’s suspended run session.
• Debug pane – enables you to view the current values and types of variables, properties, and VBScript or C# in a test’s suspended run session.

16. Smart Regular Expressions

There is a new feature added in UFT where we can add regular expression smartly with lot of available options.

17. REST Service

We can load REST service and test it as same as WebService.

18. Share Activities in UFT

Now we can share activities across UFT

• Sharing it to local (File System)
• Sharing it to ALM

19. UFT Solutions

Solutions bring together all types of testing documents in to a unified container to organize testing sessions

Ex: you can combine GUI and API tests and components and BPT tests in to one solution

Actions, QTP Tests, Application Areas, API Tests.. etc. have been added in above Solution

20. Run step feature for API tests

For Service Test API test users, this feature is a simple change but an absolutely killer enhancement that’s going to save me a lot of time–the ability to run any step on the canvas areas using the new “Run step” command.

If you have an API test made up of 50 operations, you’ll no longer need to run the whole test from the top. Simply right click on any operation on the Canvas. For instance, selecting “Run step” will run only that operation. Sweet!

21. Supports Open Source CI Systems

HP UFT 11.5 will support open source Continuous Integration(CI) systems like Jenkins and Hudson. For people with non-development background - CI is a practice normally used in a multi-developer environment where all developer codebases are merged with the main codebase several times a day

Downloading UFT 11.5 tool

HP ALM 11.5 is already available now. You can download ALM 11.5 using this link

http://www8.hp.com/us/en/software-solutions/software.html?compURI=1172122#tab=TAB3

Guidelines of SAP TAO Test Automation

Overview

Before the application of SAP TAO there was a clear separation of roles for test automation. There is the Subject Matter Expert (SME), who defines the business process and brings in the necessary understanding of the application to be tested and the entire system – and there is the Automation Engineer (QTP expert, VBs expert) who defines and manages the resources that are needed to create and work with business components as well as create VBS functions or debug in QTP.

With SAP TAO this roles are not that differenced anymore because there is no need to create complex visual basic script in QTP anymore. SAP TAO simply scans SAP screens and generates the visual basic script which links to the TAO libraries.

 

SAP Test Acceleration and Optimization (TAO)

SAP Test Acceleration and Optimization generates automatic tests during regression testing of SAP solutions, quickly. SAP Test Acceleration and Optimization creates tests and components from the screens of a transaction or the views of a CRM web application, and parameterizes them. These tests are for a single transaction or CRM web application and can be combined into a scenario test. SAP Test Acceleration and Optimization also maintains components and tests by integration into the Business Process Change Analyzer in SAP Solution Manager.

                  HP Application Lifecycle Management – Quality Center       (HP QC)

HP Application Lifecycle Management (ALM) is browser based test software that enables you to manage the application lifecycle from requirements through readiness for delivery from a single repository, consistent user experience and customizable dashboard. Cross-project reporting and asset sharing enable consistent processes, progress tracking and reporting, and asset sharing across projects. And dashboards and reporting capability let you track application readiness across the lifecycle, using KPIs to analyze data about milestones you define.

HP Quality Center offers software quality assurance, including requirements management, test management and business process testing for IT and application environments. HP Quality Center and HP Performance Center are components of the HP Application Lifecycle Management software solution set.

         HP Quick Test Professional (QTP)

 

HP QuickTest Professional software provides functional and regression test automation for software applications and environments and is part of the HP Quality Center tool suite.

HP QuickTest Professional supports keyword and scripting interfaces and features a graphical user interface. It uses the Visual Basic Scripting Edition (VBScript) scripting language to specify a test procedure, and to manipulate the objects and controls of the application under test.

 

Workflow

    SAP TAO

 In the following the different functionality of the used modules in TAO are described and a quick introduction will be given. For detailed information about these and other modules please read

SAP Test Acceleration and Optimization User Guide.pdf

Attenention

Press always on ‘Cancel’ when the following dialog “Configuration of Runtime Libraries” is shown.

This avoids an unwanted overwrite of the cBase library.

 

     Switching between central and local TAO library

When you have a local copy of the cBase files on your system for development purposes before you do changes on the central cBase do not use the TAO configuration to switch the path to avoid unwanted library backup etc. from TAO. Please do only change the value of the local file path or environment variable.

      Design

 In the Design module you can create new Process Flow Analysis (PFA). A PFA records all actions you are doing on the screen in a SAP transaction and creates the test script with it. Therefore one PFA belongs to one transaction. While the recording all used user interface objects according to the transaction are being inspected and will be processed in scripted business components. More to the topic components you can find under headline 3.3.2.1 Business Components.

Also an excel sheet will be automatically created for each PFA where you find all input parameters you used executing the SAP transaction, called DataTable. This table has an interface function to transfer all parameter values for the individual test executions. These excel files you can find in:

C:\999_SAP-TAO\DATA

While running a PFA a temporary XML file will be created called Tao Execution Context. It is located in:

·     %Temp%\TaoExecutionContext.xml

This file logs all entries and transfers to the DataTable excel. Because a test case usually contains several PFAs it has to be ensured that the transactions are working with the resulting data from the previous transactions. This is enabled by specified QTP scripted business components with parameters to transfer the data. More on that topic is to find under headline 3.3.2.1 Business Components.
 

1               Preconditions for a successful PFA recording

In order to create a PFA you can use the following checklist as a help to make sure that you considered all the needed aspects.

ID	Checkpoint for PFA preconditions
1		Set your local Windows time zone setting to the time zone of the cbFC system under test to avoid date and time conflicts with dynamically created test data. Different time zone settings between cbFC server and automation execution client.
2	Set your local Windows regional settings for date, time and number format to “Country Specified”.
3	Set your local Windows display language to “English (US)”

              Reuse of Components versus creating a new PFA

Before you create a new PFA you must always check if you can reuse an existing component. Do not create redundant PFAs.

              Creating a PFA

1.   Go to Design module

2.   Click on New in the Executable Objects section

Select the needed executable SAP transaction
Name for analysis is already populated with time stamp concatenated to it. You may change it.

1.   Click on New on the PFA tab

2.   Define a suitable name according to the PFA naming convention

•          PFA_[Test Case ID]_[Transaction-ID]_[Variant]

•          The Test Case ID is referencing the test case for which the component was initially created.

•          The Variant indicated the different component variants for the same transaction

e.g. PFA_1.3.140_NAFTA_E_FB60_001

3.   Choose Start for Process Flow Analysis.

The transaction is launched on the managed system along with the following PFA controller 

1.       Execute the process flow as a business user. Use the Test Automation user credentials.

2.       Add necessary validation points by clicking on Add Checkpoint in the PFA controller and select the desired SAP GUI object on the screen. An iteration of the component CheckProperty will be created in the script.

3.       After executing the transaction completely, stop the PFA by clicking on Stop the PFA button in the PFA controller window.

4.       A report is generated which captures the activities performed by business user.

5.        Then click on upload. This activity will upload components for the screens touched by user, to HP Quality Center and creates a parameterized test case. An excel sheet is created where the values entered by the user are captured. The draft test cases will be having the library components e.g. Initialize script, launch and log on etc.
The PFA is uploaded to the folder specified in the TAO configurations.

6.        Rework Test Data Spreadsheet.

    Checklist for limitations of PFA with SAP TAO

In order to successfully record a PFA you must consider the limitations of SAP TAO PFA recording. The following checklist gives you advice how to avoid known limitations (compare SAP note 1378813 - List of Limitations of SAP TAO Release 2.0).

ID	Limitations of PFA Recording
1	SAP GUI Scripting related limitations The limitations which apply to SAP GUI Scripting also apply to SAP TAO when recording Business Processes or executing Tests (Compare SAP Note 587202 - Restrictions when using SAP GUI scripting, Version 8 from 25.10.2011).
1a	This concerns for example the SAP GUI "Drag and Drop" functionality. In consequence it is neither possible to record Business Processes with TAO PFA when using "Drag and Drop", nor is it possible to execute Business Process tests which were created on those recordings.
1b	F4 search help control (amodal): The control is not supported in the scripting. Instead, a standard dialog is opened. In some transactions, this dialog does not open and a short dump occurs due to an error in the application. Until a Support Package corrects the application, you can work around this error by choosing the "Help->Settings->F4" menu path to select the modal dialog manually.
1c	SAPscript: The text control of the SAPscript component is not supported. It is replaced by a line editor, as described in Notes 64634 and 100358 (point 10). If you have additional questions, contact the component BC-SRV-SCR.
1d	Missing support in individual transactions: Certain transactions use dynamic keywords when communicating with the SAP system; these dynamic keywords change each time the transaction is called. This problem may occur when you select entries from the menu of the toolbar control in particular. If the script that is recorded in this transaction is run again, errors occur due to invalid parameters (for example, in the method SelectMenuItem). Note 217437 contains a list of affected transactions from the MM area. If you have questions about this problem, contact the application component MM-PUR-PO-GUI.
1e	Missing support in individual transactions: Certain transactions use dynamic keywords when communicating with the SAP system; these dynamic keywords change each time the transaction is called. This problem may occur when you select entries from the menu of the toolbar control in particular. If the script that is recorded in this transaction is run again, errors occur due to invalid parameters (for example, in the method SelectMenuItem). Note 217437 contains a list of affected transactions from the MM area. If you have questions about this problem, contact the application component MM-PUR-PO-GUI. Extract from 217437 Version 9 from 27.06.2013: ME21N (ME22N and ME23N) or ME51N (ME52N or ME53N)
2	Vertical Scrollbar of SAP GUI Scrolling vertically on a SAP GUI is not supported when making use of the mouse pointer to push/pull the scroll bar handle and that scrolling triggers a server round trip: Although moving the scrollbar like that may be recorded successfully within TAO PFA, it will be impossible to use the subsequently created tests. This is amongst others due to window size dependencies of the scroll mechanism. Workaround: Please scroll with the help keyboard shortcuts or by means of mouse clicks on the scrollbar arrows.
3	Dynamic UIs Inspection only supports static SAP GUIs (Dynpros). Dynamic SAPG GUIs which are composed at runtime will not be detected by the inspection, thus the inspection can not retrieve the structure information of such UIs from the Data Dictionary of the managed system. This limitation impacts also the recording with PFA as inspection is an inherent part of it. […] Since SAP TAO 2.0 SP2 we do not recommend the usage of the UI Scanner anymore. Please use the PFA (Process Flow Analyzer) to record the business process and to subsequently generate components and tests: If possible, then screen components related to the dynpros will automatically be generated. If this is not possible (e.g. dynamic screens), then the test sequence uses technical components which completely represent the recorded scenario.

    Checklist for reworking a PFA recording with SAP TAO

In order to rework a PFA after recording you must use the following checklist to make sure that you considered all the needed aspects.

ID	Checkpoint for PFA Recording
1	Test Data Excel: Format it according to template.
2a	Add Excel formulas to the Test data excel for manipulating data, e.g. to extract a document ID from a status messages or change data formats e.g. To make sure that a String like Material_ID can be incremented you need to split it into letters and numbers so that you can increment the number. Afterwards you need to concatenate the two pieces back to one. e.g. How to extract the needed number out of a string:
2b	Avoid excel cell format “Number”. Dependent on your computers windows location setting the decimal point is either ‘,’ or ‘.’ which may lead to failures in test execution when a different windows location setting is used.
3	Test Parameters: Promoting Component Parameters to Test Parameters of InitializeContext and parameters with links to additional files (e.g. PI Simulation): Use component parameter name as test-parameter name.
4	Labels of GUI-Objects appear in a TAO execution report: Make sure the label names are meaningful to enhance the TAO execution report. e.g.
5	Log-Off-Component: the Log-Off is used to be the last component in the structure
6	SetInExecutioncontext: ·         Add this component before the Log-Off-Component when you have to store values in the execution context. ·         Naming convention for execution context parameters: Use only upper case letters and separate the words with underscores, e.g. MATERIAL_NUMBER ·         If you have to add more than one parameter, then use an additional iteration instead of adding an additional component.
7	After each checkpoint the component CaptureScreen has to be added.
8	Delete unnecessary component e.g.: -          Unnecessary recordings by mistake -          The SetFocus Component before entering text into a field can usually deleted without impact. -          Sometimes several instances of the same screen component with the same name are created. In that case summarize all inputs and use only one screen component instance.
9	When you have to change the components VB code, save the changed component with a different name according to the naming convention (add the post fix “_changed” to the component name) and add an explanation to the component description.
10	The created PFA’s should be stored – depending on their status - in the following folders in HP QC: Development work area: ·         Folder „PFA\Design“ Approved area: ·         Folder „PFA\Ready“ The corresponding Data Tables, also depending on whether they are under construction or not, have to be stored in: Development work area: ·         Folder "C:\999_SAP-TAO\DATA\01.UT" Approved area: ·         Folder "C:\999_SAP-TAO\DATA\02.IST"
11	Once the PFA upload to HPQC is completed you will sometimes get a notification “The following PFA’s are obsolete. Do you want to consolidate them again?” select “NO”.
12	Screens with Collapse/Expand buttons e.g. for purchase order header and item details à Automation was done with already expanded details, but after system refresh details are collapsed ·         Add a PressKey for expanding all details (maybe several keys like “F3”, “F5” etc. for each detail section) to the automation.
13	Table columns à Risk: After system refresh columns are not visible, because of reset views a.         Add to automation: Select standard view and add required columns and do not save… b.         Create a special view “Test Automation” with required columns. Be aware that this view disappears after a system refresh. So you have to document the view details somewhere or create a script to create that view…

     Consolidate

While creating a PFA for each action executed during the recorded transaction, a scripted business component was created and set to right order. After you uploaded the PFA to QC Test Lab you may want to change some settings or insert a custom component to the test script. If you run the test now each component gets opened separately in QTP and the contained VBScript will be executed. This costs a lot of performance and time.

To avoid this, the PFA with all its components should be consolidated to one component. This means that the VBScript of the different components gets concatenated and only have to be opened and executed once in QTP. This also brings a functional advantage to handle the test cases in QC. Consider that consolidation here means to consolidate all components of one PFA to one component. The consolidation of the different PFAs to an integration test will be done in QC Test Plan.