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 5.7Scope6.0+ A scope can be used to narrow the search area for components. This is useful to make component references unique or to improve the readability of a test. Example: There are three panels with address data with identically labeled text fields. The scope can now be set to one of the panels. Now the specified SmartIDs refer exclusively to the fields in this panel. Scope can…
Version 7.1.4 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.4 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.4 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.4 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.4 29.5Scenario files Apart from defining single test cases you can also specify the entire test scenario in Excel files or even within your test management tool. In our sample we will go on using Excel to keep things simple. Of course it's also possible to use your testmanagement tool there. For reasons of simplification we have used Excel files again. You can find a sample test suite…
Version 7.1.4 27.3Maven People who are using Apache Maven (http://maven.apache.org) as build system may easily integrate QF-Test in their build. This can be achieved by using the antrun plugin of Maven. A demo pom.xml file, where QF-Tests tests are executed in the test phase could look like this:
<project xmlns="http://maven.apache.org/POM/4.0.0"
…
Version 7.1.4 26.1HP ALM - Quality Center 26.1.1Introduction The current integration of QF-Test and HP ALM - Quality Center utilizes the built-in VAPI-XP-TEST type of Quality Center. Figure 26.1: Integration with ALM - QualityCenter The VAPI-XP-TEST type is intended to be an automated test case for any test-tool. QF-Test comes with a template file for the VAPI-XP-TEST script, which is…
Version 7.1.4 26.2Imbus TestBench 26.2.1Introduction The current integration of QF-Test and the TestBench consists of two parts: Creating a QF-Test template file using the TestBench interactions. Importing QF-Test results into TestBench. You can find all required libraries and test suites in the folder qftest-7.1.4/ext/testbench/Version_1.1_TestBench_2.3. Please take care to copy all test suites…
Version 7.1.4 26.5TestLink 26.5.1Introduction The current integration of QF-Test with the open-source tool TestLink consists of two parts: Generating template test suites for QF-Test from the planned test cases of TestLink. Importing QF-Test results into TestLink. 3.5.1+If you use TestLink 1.9.4 or newer you can use the TestLink API for interacting with TestLink. The TestLink API requires a valid…
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.