Wednesday, January 7, 2015

Obstacles of QTP


HP Unified Functional Testing runs primarily in Windows environments. It relies on largely out of date Windows-only technologies such as ActiveX and VBScript which is not an object oriented language.
HP Unified Functional Testing cannot test with all browser types and versions. In particular it does not support Opera.
The Test Execution engine is combined with the GUI Test Code development IDE, so there is no way to run the tests dissociated of HP Unified Functional Testing, even though remote execution is still possible with HP Unified Functional Testing running on a different machine.
High licensing costs often mean that the tool is not extensively used in an firm, but instead is limited to a smaller testing team. This uplifts a archived approach to QA/testing where testing is performed as a separate phase rather than a joint approach where QA/testers work closely with the business and development teams (as is advocated by newer agile approaches to software development.)

No comments: