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.5 39.8Debugger options These options modify the behavior of the debugger. Figure 39.36: Debugger options Enable debugger (User) By default the debugger is disabled unless this option, which can also be modified through the menu item »Debugger«-»Enable debugger«, is activated. If a test is interrupted by a breakpoint or be pressing the "Pause" button, the debugger is activated…
Version 7.1.5 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.5 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.5 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.5 47.4Line breaks under Unix and Windows The difference in the treatment of line breaks between Unix and Windows is a well-known problem. While Unix uses a single LineFeed character ('\n', hex 0x0A) as line separator, Windows uses the combination CarriageReturn/LineFeed ('\r\n', hex 0x0D0A). Java automatically converts text as needed which generally works well. However, the XML…
Version 7.1.5 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.5 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…
Version 7.1.5 47.5Quoting and escaping special characters A common problem for most complex systems is the treatment of characters with a special meaning. A typical example are blanks in filenames. To specify such filenames on the command line, they need to be protected either by using double quotes or by escaping the blanks with a backslash character ('\'). Since QF-Test makes use of special…
Version 7.1.5 46.1Weighting of recognition features for recorded components When searching for a component, QF-Test calculates the probability with which each component in the SUT corresponds to the searched component. The component with the highest probability is then used, as long as that this probability is above a freely configurable threshold. First, the probabilities of the windows in the…
Version 7.1.5 47.3Regular expressions The regular expressions that you can use in the search and replace dialogs and in places like the 'Feature' attributes, the 'Primary index' of an 'Item' node or in checks all use standard Java regexp syntax. Before QF-Test version 3.1 the default was the GNU regexp package (see also appendix F). It can still be activated via the option Use old-style GNU…
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.