Si vous ne trouvez pas ce que vous cherchez, essayez encore une fois avec des "guillemets", par exemple "windows 10" au lieu de windows 10. Plus d'informations sur la recherche
Version 7.1.4 SWT39.7SWT options The following options are used specifically for SWT testing. Figure 39.35: SWT options 4.5+Connect without SWT instrumentation (System) Server script name: OPT_PLAY_SWT_VIA_AGENT With this option activated there is no need to instrument SWT based applications, except for older SWT versions on Linux. For detailed technical information please see section 45.2.…
Version 7.1.4 5.8Generic components Before the introduction of the SmartID in QF-Test Version 6.0, generic components were the pattern of choice for avoiding recording components. With SmartIDs, this goal can be achieved easier and more flexibly. Still, the concept of generic components is described here for backwards compatibility. A typical use case is the testing of localized applications.…
Version 7.1.4 3.5+53.3Daemon security considerations Anybody with access to the QF-Test daemon can start any program on the daemon machine with the rights of the user account that the daemon is running under, so care should be taken to only allow trusted users to connect to the daemon. Of course the QF-Test daemon should always be run on a machine that is protected from outside access by a…
Version 7.1.4 52.11.2The DocumentNode class Web The root document of a web page is not represented by a 'Window' node, but the special node 'Web page'. Nested document nodes in frames correspond to 'Components' nodes. The DocumentNode class is derived from Node and also resides in the package de.qfs.apps.qftest.client.web.dom. In addition to the methods defined in the Node class and explained…
Version 7.1.4 Web52.11Pseudo DOM API To a certain extent QF-Test exposes the DOM of a web based SUT to 'SUT script' nodes. This API is not equivalent to working directly at the JavaScript level which can be done via the methods toJS, callJS and evalJS described in this chapter. With this API is possible to traverse the DOM and retrieve and set attributes of the respective nodes, but not to…
Version 7.1.4 47.1Drag&Drop From the beginning Drag&Drop has been hard to implement in Java. JDK 1.1 had no Drag&Drop support at all and the first steps taken with JDK 1.2 were far from satisfying. In JDK 1.3 Drag&Drop has matured, but there are still problems with stability. That Drag&Drop is so hard to get right is partly due to the fundamental difference in the way Drag&Drop is implemented by…
Version 7.1.4 47.6Include file resolution This is a section you should hopefully never need to read. It explains in detail how implicit 'Procedure' and 'Component' references are resolved during test replay. If you need to read it, your test suite include hierarchy probably is too complicated and you should consider simplifying your includes. There are basically two scenarios in which QF-Test must…
Version 7.1.4 Swing45.1JRE deinstrumentation Note JRE instrumentation has been obsolete for a long time now and can even cause problems. The following section remains only to provide background information and to show how to remove an existing JRE instrumentation without reinstalling the JRE. Note To remove instrumentation of a JRE you need write permission for some of its directories, so you may…
Version 7.1.4 4.0.3+52.8ResetListener During test development you sometimes want to stop all connected clients and reset all dependencies as well as delete global QF-Test variables in order to establish a well defined starting point for the next test execution. For that purpose QF-Test offers »Run«-»Reset everything« in its main menu. To accommodate their particular needs test developers can…
Version 7.1.4 46.2Generating the component 'QF-Test ID' QF-Test uses the following algorithm designed for the best possible assignability of GUI objects when creating 'QF-Test IDs': The 'Name' attribute of a 'Component' has a value: The value is used for the 'QF-Test ID'. No 'Name', but a 'Feature' is available: This value is used for the 'QF-Test ID' and prefixed with the value of the 'Class…
Nous utilisons des cookies "Matomo" pour l'évaluation anonyme de votre visite à note page web. Pour cela nous avons besoin de votre consentement qui est valable pour douze mois. La révocation est possbile n'importe quand sur notre page "Protection de données".
Configuration de cookies
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.
Name
_pk_ref
Provider
Matomo
Lifetime
6 months.
Type
HTTP
Description
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
Name
_pk_ses
Provider
Matomo
Lifetime
1 day.
Type
HTTP
Description
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.
Name
_pk_testcookie
Provider
Matomo
Lifetime
Session.
Type
HTTP
Description
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
Name
_pk_cvar
Provider
Matomo
Lifetime
30 Min
Type
HTTP
Description
short lived cookies used to temporarily store data for the visit.
Name
_pk_hsr
Provider
Matomo
Lifetime
30 Min
Type
HTTP
Description
short lived cookies used to temporarily store data for the visit.