What is RTL (runtime (runtime library)? library)? The runtime library can generate an SAP Test Acceleration and Optimization report for each test Execution The generated Test Acceleration and Optimization reports are stored at “Logs”. There is a subfolder per test execution, at that location. The name of the subfolder depends on how the Script was started. The “Business Process” prefix is used when the test is run from HP Quality Center The “Business Component” prefix is used when a component is executed directly from Quick Test Professional What is your application Area? The application area is an HP Quality Center concept which ensures only loading the libraries that are relevant for the test component. The application area used by SAP Test Acceleration and Optimization tests and tes t component is _SAP_Doc How will you Capture Inquiry number from SAP TAO (need to read Inquiry number and to be used for Quotation) without using QTP? The “Get Message “Get Message Parameter” component gets the value of one of the message parameters of the Status Bar. The subsequent component can retrieve the persisted values using the corresponding tokens: %VA21_MessageStatus% %VA21_MessageParameter0% %VA21_MessageParameter1% How do you configure SAP TAO?
What is UI Scanner and Inspection? it scans the screens i.e. means when you insert a transaction code when you click on execute , QTP will launch and generate a script here you will not touch with any QTP script once you scanned automatically scanned component will be uploaded into QC and when execute this , QTP will launch and execute the script. Inspection: will just insert a transaction and breaks the screen into multiple pieces (Business components). Then you Design the test case then will upload script into QC What is the boot strap in SAP TAO? Bootstrap Library CBASE_init.vbs.txt is the entry point to the runtime library initialization. The initialization steps are performed by the bootstrap library “CBASE\ “CBASE\CBASE_Bootstrap.vbs”. This bootstrap library is responsible for: Reading the CBASE.Config file Initializing the SAP Test Acceleration and Optimization execution contex t Loading all other core libraries Initializing the log & traces Initializing the SAP Test Acceleration and Optimization report
What is consolidate view and use of it ?
In a simple Consolidation is nothing but you is just consolidating all your components in single component and making a final component and will increase the performance of the script. Ex: using PFA or UI Scanner you will record a transaction Difference between QTP Object Spy and SAP TAO object spy?
The SAP Test Acceleration and Optimization Object Spy is a tool, which provides detailed information about the SAP GUI Controls. Object Spy is typically used to identify a control. ----------------------------------------------------------------------------------------------------------------------------------------1. Change Analyzer & Inspection do the same job to find changes in the SAP system isnu2019t it? How different are these two other than Change Analyzer repairing the broken components? Change Analyzer & Inspection both are different . Change Analyzer helps us to analyze the impact of changes due to upgrades, SAP patches or Custom development on a test, components or consolidated component. Inspection - It is a another type of recording option using Screens & it enables us to select multiple SAP GUI screens and transactions for testing in an easy to use interface once you start inspect the transaction. 2. What is the need for consolidation? We can directly upload transactions to QC isnu2019t it (without consolidating) you can do it but consolidation enhances the performance of an automated test script by removing the fields that are not required for a business process. It takes a test script and generates a master component that includes all the QTP code of every component, into a single one. 3. Where does QTP come into picture here? Everything is between SAP TAO & QC isnu2019t it? For the project purpose we have to integrate QTP with QC, isnu2019t it? Or is it mandatory to have QTP. Yes it is mandatory to have QTP because all SAP TAO components built in QTP whenever you execute it runs the script in QTP and also if required you need to create your own components btw you also need to have BPT & Solman for enabling license. 4. Also I didnu2019t understand the integration between UI Scanner & QTP. UI Scanner Scans most of the editable components of the SAP screen and creates component because when you launch UI Scanner, QTP also will open as I told you components are built in QTP.
Q1. Does Inspection generate test scripts in QTP? Q2. When you say: " you can do it but consolidation enhances the performance of an automated test script by removing the fields that are not required for a business process. It takes a test script and generates a master component that includes all the QTP code o f every component, into a single one." Does this mean, TAO generates a respective QTP code for various business components that we create using PFA/inspection? And when we create a Test Case in Test Plan & Consolidate it, does it consolidate those QTP scripts into one? Does consolidation remove the objects in Object Repository (QTP)that are not required for the test script execution? Q3. When you say "Components are built in QTP" does it mean scripts & related object repository or built?
All my thought are revolving around how QTP is integrated with SAP TAO. Can any test case be maually executed using SAP TAO?
-
1 . PFA & Inspection - As you said these are the 2 recording options. What is the use of PFA over Inspection or viceversa. What is recommended to use. - Records the activities performed and create a components of the screen touched by the user.It also creates a excel sheet which contains the data entered by the users. This components can be uploaded into QC. It's a easy recording and time saving and if you have multiple screens , you can easily record with out spending much on time on building a test script using components. Even SAP recommends to use this option for recording. 2. Inspection & UI scanner - Again I can see there are 2 options in 'Inspection' tab. In project every one is confuse when to use 'Inspection' and when to use 'UI Scanner' and then we have PFA as well. Dont know how to manage. - Inspection :insted of recording , it will enable us to select multiple SAP GUI screens and make a component. But based on the screen a nd number it's tough to i dentify which screen it belongs to. for example VA01 selection screen has some xxx number so you can select that screen and can do inspect so it will build a selection screen component insted of recording. but here challenge is you need to know the screen number if you go to SAP and system and status u will find the screen number based on that you need to select screens and it's just an option. But i dont recommend to use this option because so complex to know screen numbers and build a component on that. UI Scanner: Scans most of the editable components of the SAP screen and creates component. like you can scan VA01 transaction code and build a component etc...
3. Consolidation - As you said - Consolidation is nothing but you is just consolidating all your components in single component and making a final component. For example adding logoff screen, capture screen etc etc. But the same thing can be done using QC as well where we arrange all components in Test Lab to make a script. Then what is the advantage of consolidation through TAO. What is preffered? Please correct me if I am wrong. -
First , you need to build a test script with componenets under test plan. i.e. it has some few componenets
so you want to consolidate and make one single components i.e. using consolidation - it generates a master component that includes all the QTP code o f every component, into a single one. advantage is enhances the performance. 4. How TAO repository is different then QTP repository? - TAO Repository: Its part of SAP Solution manager system. Its used to store User interaction and sequence of the screens in a business proces. It also stores Information specific to SAP Test Acceleration and Optimization that cannot be retrieved by other tools. & you can repair your componenets. and its useful when you want to upgrade your TAO.
- QTP Repository: Simple you can add your objects into local or shared repository and you can make use o f this objects and build a script. you can google it , will have plenty of information on QTP object repository. it's a imp. concept. 5. Today when I was trying to record a transaction (VA01 - create Order) using Inspection and then UI Scanner, the inspection and scanning was successfull but got the error message in Inspection it was 'Component upload failed; screen might be empty' in UI Scanner it was 'Component cannot be created' Two things : one is, please see the log file or else check your error log report. and also try to upload once again and see if u receive any errors. second things ,make sure your UI scanner folder path is correct and select UIScanner_10 folder in the path and check create component checkbox then try and still if it not working then there is a problem with your UI Scanner "Script.MTS' file. so if you go to programfiles under TAOUIScanner folder under Action1, you see "Scripts.MTS' file and you need to check that.
SAP TAO: Get and Set Value from/to Excel Hello, as i do not have any documentation yet, i ask this SAP TAO Question to the community: Can anybody explain, how i make Getter and Setter from/to Excel Files in SAP TAO?
1.
I want to read a value from a excel with TAO and check in SAP if the value in the SAP GUI is th e same as in my Excel. e.g. i have a quantity in my excel and i want to check, if the current production order has th e same quantity.
2.
I want to read a value from a production order with TAO and want to write down this value to the excel with TAO.
You can use the following default business components from sap tao which is available in SAP front end / R3. From SAP to Excel ( you have to pass on the correct parameters in accordance to the physical/logical properties of that object) 1.Get Text 2.Get Cell Value 3.Get Status bar content 4.Get Message Parameters For checking from Excel: 1.Compare Values 2.Set Condition 3.Report Message Also you can use standard tokens like %random% in excel for P.O Numbers which automatically fetch six digit unique values...No need to change everytime... Hope this helps
.
Storing the Sales Order Number in the Data Table Excel Sheet 1. Drag and drop the getMessageParameter component in the suitable location of the test case. Generally, it would be dragged and dropped before the automatically added GetMessageParameters component.
2. Provide the same URI of getMessageParamters component to the getMessageParameter component. Use the suitable index for storing the value. You find this index by using QTP object spy. The index in the case of standard VA01 transaction is 1.TargetField is the DT_XXX which is a column name in the data table Excel sheet.
Adding Manual Validation on the Status Bar 1. While recording the PFA use the CheckPicker functionality to inject the CheckProperty component for status bar validation.
2. After the PFA upload, the check property component is introduced after the GetMessageParameters component. 3. Modify the data table Excel sheet to capture suitable string for validation.
1. What about the execution of existing tests and components which were created with version of SAP TAO previous to 2.0 SP2 ?
Tests which were created with earlier releases SAP TAO 2.0 sp02 will still be executable even in TAO 2.0 SP02 and behave the same way a s before. There is no migration needed to run those formerly created tests. The only drawback will be that the old tests will not benefit from the performance improvement or enhanced capabilities coming along with the new SP02 libraries as they still use the old libraries. Please note that this also applies to custom components.
2. What about modifying and maintaining existing tests and components which were created with version of SAP TAO previous to 2.0 SP2 ?
Tests which were created with earlier releases SAP TAO 2.0 sp02 can still be maintained. The rule is simple: there should not be mixture of old tests and new components. As a rule of thumb, tests created with versions inferior to TAO 2.0 SP02 can still use former default components (located under Components/SAP R3). Former default components are still supported in existing tests.
3. What about modifying old scripts using n ew components ("mixed environment")?
This is definitely not recommended. Former tests should stick using former components (located under Components/SAP R3). The new features (alvs, multi languages, performance) are only accessible through new components and are therefore not applicable to former tests and components. The enhancements are ONLY included in tests recorded with TAO 2.0 SP2 or completely based on the new default components.
4. What components should I consider if designing my test manually directly in QC? o New tests should only make us of the new default components thus collecting all the enhancements that these provide. O In case of an automation scenario that is not 'implementable' with the new d efault components (located in SAP Front End) then it is recommend to inform SAP of this lack (feature request) and to fallback to e ither a custom component (implemented by the customer) or, but this should be very rare situations, to former default components.
5. What is the paradigm shift of the new CBASE introduced with SAP TAO SP02? The new CBASE is directly interfacing with the SAP GUI Scripting API, while the old library is interfacing with the
QTP SAP Add-on. This means that the new CBASE makes use of the powerful SAP GUI Scripting API which is controlling the SAP GUI. This makes a real difference concerning performance and usable GUI controls, same time implementation of custom components becomes much easier. Notions introduced by QTP like regular expressions for control search or relative IDs are not needed anymore (and are thus not supported anymore) in the new CBASE libraries. Documentation of the SAP GUI Scripting API is directly accessible at the SAP GUI. Hint: In case you have to implement a custom component, then it is always a good idea to use the SAP GUI Recorder in order to create a sample script as the recorder uses nothing else than the SAP GUI Scripting API.
