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

Comments

  1. 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. 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

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.