In the end we ended up publishing custom COM components which the VBScript called into and used QTP/Quality Center as a half-assed reporting engine that didn't really offer enough flexibility to get the type of reports we really needed.Īnother problem with Mercury/HP is that they outsourced all of their tech support to India and didn't train them. Once the test is done copy all the results to the parent test and then remove the QTP test from the test set. We were doing things like run a test that dynamicly adds the QTP test to the test suite, edit the input parameters, change the object repository so that it matches the enviroment, save the test, spawn a scheduler instance in order to run the test. There are all these hacks and tricks we had to do in order to get any sort of extensibility. QTP/QC is based on ActiveX/COM and can only be scripted with VBScript which is another bag of flaming dog poo. Record could only be used in order to build up the object database and even then had to result to all sorts of hacks in order to get it to work somewhat reliably. The record/playback functionality was horrible, it would routinely get confused resulting in weird test results. I was head of an automation team that used QTP and I hated it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |