 |  |  |  |  |  |  |  |
| Version 7.1.2 |
At the moment QF-Test primarily supports functional testing of Java and Web applications. We are working on a comparable module for testing native MacOS applications with equivalent processes and features. The module described in this chapter provides a temporary solution when simple control of native MacOS applications is required during testing of process flow across Java, Web and MacOS applications.
The module allows control of native MacOS GUI elements via the MacOS Accessibility interface. It can trigger actions and check certain values. Further information about this interface can be found in the corresponding documentation.
Procedures in the standard libraryqfs.qft wrap the methods of the module most frequently required.
It is not possible to record actions or checks directly (capturing). The parameters identifying a GUI object need to be determined and then be passed to the respective procedure.
Actions are replayed via 'hard' system events mainly. This results in a different replay behavior than you are used to with QF-Test for Java or web applications.
Despite these restrictions the module can be very helpful for simple testing and controlling tasks on native MacOS applications.
| | | | | | | Last update: 3/13/2024 Copyright © 1999-2024 Quality First Software GmbH |
1. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
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.
