Skip to main content

QTP Glitches So Far...

Well, I have started work on QTP after having worked on couple of functional test automation tools like – Selenium and Test Complete.
My first impression with QTP has not been very positive; herein I have listed few glitches I experienced so (I can only hope this list not overgrowing with time)
  • No Refactor of code – so if u modify a function name in one place it has to be updated manually in all function calls
  • “General Run Error” – try to check a check box which is disabled and you receive “General Run Error”! Can’t it say object is disable
There have been other mysteriously intermittent instances of “General Run Error” about whom I am still groping in dark
  • If used ExecuteFile to get function definition in Action then there is no way to jump to function definition from action. Function has to be opened manually. (I don’t associate function library as it is going to hardcode path to function)
  • While running QTP tests on a System it can not be used for any other task, QTP keeps bringing browser to top on which tests are executed
  • QTP on locked system, File Upload just does not work on locked system
  • Keep shared repo opened while executing test and be ready for unknown errors
  • Unable to test API on fly (It is Test Complete feature I love most), so if you want to check Web Table data – GetCellData(row, column)
Then you should execute it in test and there is no way to tests it from Object Spy itself
  • Some time have static screen while executing test and I keep waiting for next action, good if there were Test Complete sort of display during test execution
SO FAR………….
THanks,
Tarun K
Labels:

Comments

  1. meMarch 3, 2010 at 1:36 PM

    I have been sitting next to Tarun and watching him carefully document all the shortcomings in QTP. In fact when our manager walked by and saw his whiteboard completely covered with bright red comments he turned and took a second look.. though that may be just thanks to his handwriting! Anyway I can attest that everything written in this article is the result of careful analysis and extensive usage of the tool :)

    ReplyDelete
  2. UnknownSeptember 25, 2013 at 2:51 AM

    That's a short list... :)
    I have many many more, but comparisons of QTP to a standard IDE aside there are many features that could be improved in QTPs UI and capability.
    You should step over to SQA Forums or HPs own forums where you can make an actual difference. This site will not instigate change I am sorry to say. Raise your list as a contribution list that everyone can list their grievances with QTP so maybe HP will start to take notice and provide us with some new millennium solutions instead of last century.
    SQA Forums is regularly perused by HP ;)

    ReplyDelete

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

Using xPath to reach parent of an element

Note: If you are new to java and selenium then start with selenium java training videos .   I prefer css locator over xPath but there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also hig...
Read more

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -
8 comments
Read more

Should selenium tests be always independent? The endless debate !!

Though unit tests have always recommended to be independent of each other, advent of selenium+TestNG has given birth to dependent integration/end to end tests. TestNG Author Cédric Beust had written about it few years ago. When I had begun writing selenium tests I used to launch browser once in one test class and test methods were usually dependent on one another. Hence 2nd test method would begin test run on same browser + application state where 1st test method stopped. Launching just one browser for five or more test methods in a class is big time saving is not it? Well not really, for the reasons I am going to describe in this post. Since then I have moved on to launching browser per test method but yet give in “charm” of dependent test methods at times. to So here are the few pros and cons for dependent tests and - Pros - Similar steps of execution don’t have to be repeated in multiple tests when steps constitutes a test method in themselves If login fails then...
Read more