Go gaga over Machine Learning

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?   Pros 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.   Cons  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 Adapte

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. Accountabilities 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 perfor

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 s

Here are some interesting things that I have tried recently changing the way automation is done traditionally. What to automate? The most difficult question though it sounds pretty straight forward If you already have manual tests have your battle is won If not run through the most used features / easily broken  Take leads from the sitemaps / access logs / Roles / analytics and access statistics Start automating? Biggest challenge is always maintenance , categorise tests into essential features and generic 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. Everything flows from QDD to WDU tests 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 rule

If you are using QTP and Reflection sessions for the first time What you will notice: Whenever you open Reflection Sessions using QTP, it stops recognizing the objects viz. TEWindow, TEScreen etc. But when we open Reflection Sessions manually and then spy, QTP recognizes objects correctly What can be done to avoide this issue: We open reflection before launching QTP (yes thats an exception) 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 Additionally we keep only one session open in reflection window Happy Testing!