Is anyone using the newest version of QTP that used SilkTest in the past and what functionality are you missing? EX, If you connected to a SQL in ST can you connect in QTP. What screens and pages worked will in ST that you are having problems with in QTP.
If you could go back to ST and stop using QTP would you?
I like ST but may need to learn QTP What areas are lacking in QTP that I might miss and have you found any work-around for the problems?
Coding for different problems in ST I found was easy, will I have the same feeling with QTP that this tool can do whatever I ask of it?
I miss the powerful object oriented 4-Test language. I have no use for the record and playback facilities built into most functional test automation tools, but QTP certainly seems to be optimized towards the "ease of use", and making the tool accessible to those with little or no understanding of the software QA process.
I miss SilkTest's appStates, and the TestCase keywords for delimiting test cases. I miss ST's Test Script and Test Case entry and exit handlers that could be overridden to execute specialized setup or cleanup functions. I miss ST's more robust and flexible recovery system.
We have found many of QTP's facilities (shared object repository, checkpoints) to be it's biggest liabilities, and consequently we avoid using them.
If the opportunity existed, I would go back to ST in a flash.
Increases your hourly rate by 25% [img]images/icons/wink.gif[/img]
No seriously Bruce could it be possible that QTP does support what you require but you haven't yet come across it? With QTP you can make ODBC or ADO calls to MS SQL or Oracle databases, fire off aSQL query and process the returned record set.
There is also the powerful Automation Object Model which the majority of users don't even bother to learn.