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 20Testing web services4.2+ From version 4.2 onwards QF-Test offers the possibility to test web services. Unlike the well known capture replay model here you must take care yourself to build the HTTP request and verify or validate the responses and/or the results. It is highly suggested to use the existing documentation of the web services you will test. For testing SOAP web services…
Version 7.1.5 46.3SmartIDs - general syntax The various SmartID features can be combined with each other. The following is the general syntax for combining SmartID features. Square brackets mark optional elements, while uppercase text signifies a placeholder: #[%][noscope:][ENGINE:][CLASS:][VALUE][<INDEX>] A SmartID consists of the following parts in the following order: # always indicates the…
Version 7.1.5 46.4SmartIDs - special characters The special characters :, @, & and % have special meanings in SmartIDs. ":" terminates a component class or UI engine. A % at the start of a SmartID signals the use of a regular expression (see section 47.3). The other characters mark the beginning of a sub-item, like a table cell. If these characters should appear in a SmartID with their literal…
Version 7.1.5 53.1Daemon concepts In daemon mode (comparable, but not equivalent to a "service" on Windows) QF-Test listens to RMI connections and providing an interface for remote test execution. This is useful for simplifying test execution in a distributed load-testing scenario, but also for integration with existing test management or test execution tools. There are three command line…
Version 7.1.5 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.5 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.5 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.5 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.5 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.5 34How to start a testing project This chapter talks about the most important aspects that should be considered before you start to use QF-Test widely in your testing project. It mostly raises questions and gives general answers with references to more detailed information. The aim of this chapter is to provide hints about issues which you should take care of in order to make your GUI…
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.