What is SAP TAO?

  • SAP TAO is an automation testing tool released by SAP in integration with focus-frame.
  • TAO (Test Optimization and Acceleration) is designed for SAP GUI based applications integrated with SOLMAN (Solution Manager) and HPQC
    • SOLMAN Provides the necessary tools around the Implementation, Operational and Optimization aspects of your SAP Application life cycle.
  • The two add-ins that are mandatory for TAO to be functional are "SAP" and "Web".

Where does QTP fit in?
  • SAP TAO wraps up QTP and QC and QTP acts as execution engine, test scenarios are created and driven from QC through business components. 
  • SAP TAO helps in automatic generation of test components for end to end scenarios.
  •  QTP and SAP TAO are really good when it comes to automation the  only challenge is  installation.
  • installation process consisting of four areas
    • Quality Center – This will host Quality Center software, patches, add-ins and SAP Adapter
    • SAP Back-end systems – This will host the SAP TAO agent.
    • Solution Manager – Quality Center Adapter has to be installed on solution manager. The per-requisites solution manager support pack levels also have to be met
    • Desktop –The desktop should have SAP GUI, QTP, and TAO installed on it
SAP TAO Modules
  1. Connect :-Connect module is used to establish a connection between SAP and Quality Center
  2. Inspect :-It contains two tabs, Inspection and UI Scanner.
    1. With the help of inspect option we can generate components locally.
    2. Upload the Components to Quality Center
  3. Consolidate :-This option helps us to consolidate all business process or components into single component for fast execution of test script
  4. Import/Export :-Use the Import/Export settings to designate a path for transferring components from SAP Quality Center to an SAP Test Acceleration and Optimization client.
How do you automate?
  1. Open SAP TAO, establish a connection between SAP and HPQC from Connect tab
  2. Use the Inspect module to specify transactions that you need to create a test script
  3. Select the screen no. which you want to automate and click inspect button. You will get the message “Inspection done” on task-bar and that component is transferred to HPQC BPT Module
  4. Log on to HPQC. Select the project . It should be the same which you have selected in TAO Connect module
  5. Drag and drop the transactions in the order that they occur in the business process requirement
  6. Parametrize the data in the SAP TAO Excel spreadsheet or the Quality Center database (Test Plan)
  7. Execute the test script and review it for any discrepancies

Installation of SAP Quality Center Adapter Note1059350 and Note1285941
Installation of SAP Test Acceleration and Optimization Note1231935 Note1341244
Information and Guides for SAP TAO SAPTAO-1, SAPTAO-2


Skillset - Automation Test Analyst

Note: the Skillset category is just to gauge where you stand in terms of the skills required for the role

Here is another really interesting Australian Job Description for a test automation engineer's role:

Position Description: An Automation Test Analyst is required to join the Client's Specialized Testing Services Group to plan Automation Testing, build and execute the Automation Scripts.

  • Conduct Automation assessments of projects to determine if the project is a suitable for Automation testing
  • Ensure Automated Testing activities are performed in accordance with established standards and processes.
  • Review and provide Automation testing input into test documentation such as the Test Strategy, Test Plan and Test Summary Report
  • Develop automated test scripts utilizing approved test tools such as QTP and HP Quality Center
  • Ensure traceability of test scripts back to business requirements
  • Create relevant test data to enable testing to be performed
  • Perform test execution of automated test scripts and report on Automation Testing results
  • Identification, investigation and escalation of defects, ensuring traceability back to test cases
  • Work to ensure testing outcomes are achieved within defined cost, time, and quality constraints
  • Capture test execution outcomes in HP Quality Center

Key Skills & Experience - Mandatory
  • Extensive Test Analyst experience in an integrated environment
  • Extensive Automation Test Analyst experience using QTP
  • Strong SAP experience
  • Extensive JAVA experience
  • Strong HP Quality Centre experience
  • Strong database and SQL skills are essential
  • Experience in the use of testing tools and methodologies
  • Excellent communication skills - both written and verbal
  • Attention to detail
  • Exposure to test middleware systems like TIBCO ; web Methods

Key Skills ; Experience - Preferred
  • Experience in XML, SOAPUI, TIBCO and Selenium highly regarded
  • Working experience using Agile testing methodologies and processes
  • Relevant testing certification such as ISTQB Certification


World Tester's Day - 9th September

Surely every day is Tester's Day, but it feels good to have a special day that can make us testers around the world share and collaborate and feel proud to be one. Now this is the second year in a row that I have been celebrating this day. If you haven't heard about tester's day then read this ! It is 68 years since the first bug was found , beat that for a metric in software testing :) I feel proud to be a testing professional and have had my own reasons to do so. Shall not ponder over that here, not on the "Tester's day".

I have been celebrating this day in a better manner now with a good bunch of like-minded testers and colleagues in the testing community. I thought why not write about what would be the best way to celebrate a day like this
Here are my few cents:
  • We started off with a simple idea of creating a badge that read “Proud to be a Tester” and some that read “Official _______ Tester” where the blank was filled with the specialized skill the tester had. For instance automation/performance/Game/mobile/database and so on…
  • If the audience isn't large you can get t-shirts printed instead of wearing those badges.
  • Apart from that we have some good fun-facts about testing that were pasted all over the premises including breakouts and washrooms.
  • We also had quizzes and puzzles related to different fields in testing that ran throughout the day.

Would love to hear from other testers around the globe , how they celebrate this day?!

Happy Tester's Day ! Keep finding those bugs...


Quick Dirty Disposable automation

Here are some interesting things that I have tried recently changing the way automation is done traditionally.

What to automate?
  1. The most difficult question though it sounds pretty straight forward
  2. If you already have manual tests have your battle is won
  3. If not run through the most used features / easily broken 
  4. Take leads from the sitemaps / access logs / Roles / analytics and access statistics
Start automating?
  1. Biggest challenge is always maintenance , categorise tests into essential features and generic
  2. What we also categorise tests into are " will there be an upgrade or not?" - so we have two sets quick dirty disposable tests and well designed unbreakable tests.
  3. Everything flows from QDD to WDU tests
  4. The first script is always a bootstrap script that will have the initialization parameters in place
By now you would have realised this is an unorthodox way and might be debatable with some test automation experts, the reason being we are ignoring the rules
The advantages:
  1. If the tests are just required for an upgrade then why make the tests so stable, quick brittle tests should do
  2. Number of automated tests churned in a day much higher than usual
  3. The QDD (Quick Dirty Disposable) tests are actually not disposed but used later if required to convert them to WDU tests
  4. Manual testers can use these tests which will give them the time to actually concentrate on the core functionality being tested

This definitely doesn't mean that we have the license for bad automation practices.Do not spend time to write quick and dirty tests for applications with a long lifespan.

Object Identification issues with Reflection Sessions

If you are using QTP and Reflection sessions for the first time

What you will notice:
  1. Whenever you open Reflection Sessions using QTP, it stops recognizing the objects viz. TEWindow, TEScreen etc.
  2. But when we open Reflection Sessions manually and then spy, QTP recognizes objects correctly
What can be done to avoide this issue:
    1. We open reflection before launching QTP (yes thats an exception)
    2. To connect/disconnect the reflection session you can use below statements:

      Set objReflection = GetObject("H:\Sessions\REF2011-PersonalCommunicationsIcons\TSYS.rd3x") ‘the path will change as per your scenario

      objReflection.Connected = 0

      objReflection.Connected = 1
    3. Additionally we keep only one session open in reflection window
Happy Testing!