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 16.2Emulator or real device At the beginning of Android testing, you need to decide how to start: with a virtual or real device. A real Android device can be used for testing with QF-Test. It needs to have the USB debugging developer option activated and requires a connection via cable to the machinge QF-Tests runs on. By help of respective setup sequence, QF-Test connects to the…
Version 7.1.5 16.4Connecting to a real Android device To use a real Android device for testing it needs to have USB debugging enabled and connected to the machine via USB cable. Also an Android SDK is required on your machine. Even though it may be sufficient to just install a dedicated package for the Android SDK command line tools we strongly recommend install the full Android Studio as…
Version 7.1.5 16.6Record actions and checks for Android Please press on the Record Button to see what is going to happen for Android testing in QF-Test. A special recording windows will open showing the content of either the emulator or the real device. This special window is necessary, as it is currently not possible to directly capture events from the emulator or real device. So you need to…
Version 7.1.5 16.1Preconditions and known restrictions 16.1.1Preconditions In order to perform Android tests with QF-Test, the following preconditions need to be fulfilled for the machine QF-Test is running on: In case an Android emulator shall be used, a sufficiently powerfull machine is required (not an old scrap mill :-). It might be even necessary to enable hardware acceleration (typical via…
Version 7.1.5 27.2Ant People who are using Apache Ant (http://ant.apache.org) as build system may easily integrate QF-Test in their build file:
<project name="QF-Test" default="runtest">
<property name="qftest"
location="c:\Program Files\qfs\qftest\qftest-7.1.5\bin\qftest.exe" />
<property name="logdir" value="c:\mylogs" />
<target name="runtest" description="Run a test in…
Version 7.1.5 5.1Components of a GUI The graphical user interface (GUI) of an application consists of one or more windows which hold a number of components. These components are nested in a hierarchical structure. Components that hold other components are called containers. As QF-Test is itself a complex application, its main window will serve well as an example: Figure 5.1: Components of a GUI…
Version 7.1.5 5.5'Component' node When 'Component' nodes are used in place of SmartIDs QF-Test stores the recognition criteria of the recorded components in 'Window' and 'Component' nodes, whose hierarchical order matches the structure in the GUI of the SUT. These nodes are located below the 'Windows and components' node. The following image shows a section of the 'Component' nodes that are part…
Version 7.1.5 27.1Eclipse Eclipse (http://eclipse.org) is an Open Source software developer tool for java applications. QF-Test offers an Eclipse plugin enabling you to start an application directly from Eclipse and run tests on it - anything from whole test sets, single test cases or even just a mouse click. Video instructions: 'The QF-Test Eclipse Plugin' 27.1.1Installation For the installation…
Version 7.1.5 29.7Adapting to your software All examples make use of the CarConfigurator of QF-Test. You can use those samples as templates to adapt the existing concept to your strategy of keyword-driven testing. The provided samples can only act as templates because of the huge variety of ways of creating applications and the many different testing strategies. They will never serve as…
Version 7.1.5 29.4Behavior-driven testing (BDT) Besides the traditional concept of keyword-driven testing a second concept called Behavior-driven testing (BDT) is widely being used. Tools for behaviour driven testing like Cucumber/Gherkin can easily be integrated into QF-Test (please contact Quality First Software GmbH for a description about how to set up and configure BDT with QF-Test). Using…
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.