For the development and execution of automated test-cases for our customer (HP / HP OpenView Software) a test tool was to be selected which had to be well-suited to testing of JAVA GUI applications. The requirements that had to be met are:
Unfortunately, many of the well known tools of the more renowned vendors met only parts of the requirements. Especially remarkable during the evaluation was QF-Test's ability to run tests on different platforms. The standard recognition of graphical components is already very powerful. By making use of the Name- and ItemResolver extension API it should be possible - even in intractable situations (none or inconsistent Object.Names) - to create a robust test-case that will run reliably even in localized environments.
One can see clearly that the features of QF-Test have been implemented very practically. Only thereby is it possible to very efficiently create test-cases, which - during the usual changes of software throughout its life-cycle (a number of years in the current case!) - can always be adapted to the latest version with low maintenance overhead. Additionally, QF-Test's plugin interface opens the way for integration into the existing distributed test framework so that development of a lot more complex test-cases should be possible.
Therefore, QF-Test came off as the definite winner of the evaluation. The fact, that its license and support costs for development and execution were the lowest wasn't even taken into account.
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.