I have been following a few threads on the following functionalities in QTP. I think these three are major drawbacks of the tool:
1. Does not allow 'on the fly' update of GUI reposatory.
Thread : Dynamically adding objects to the Object Repository in QTP..
Impact: Scripting Overhead .. have to use descriptive objects.
2. Does not allow me to fine tune script execution speed beyond the two options of 'normal' and 'fast':
Thread : How to slow down script execution
Impact: Affects robustness of your automation suite. will give inconsistent results.
Its not a practical solution to put wait statements after each step of ur test.
3. For a failure in result, does not provide me with a link to the failed statement in the script. (<Ctrl-S> in WR, double-click in Silktest etc)
Thread : Link result to script????
Impact: BIG BIG maintainace overhead. I have to note line number and the script name and then navigate to it.
If all/some of the above are not correct, can someone post the solutions here?
If they are correct, is some mercury guy snooping around for customer feedback/enhancements?.. I sure hope he is!!
2. - 'Normal' & 'Fast' mode, most of the time there is little or no difference in the actual execution speed between these two modes. Don't use wait statements use Wait Property or exist they are more efficient.
As for Mercury being interested in feedback forget it. The number of times I've seen a post on the MI Support site for an enhancement to allow the renaming of checkpoints without MI actually implimenting this is a joke.