Manuel
 

TopTable of contentsPrevious Chapter: 30.6 Custom test case descriptionNext Page: 31 Usage of QF-Test in Docker EnvironmentsChapter Overview: 30 Keyword-driven testing with QF-TestPDF versionQF-Test
Version 8.0.1

Adapting 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 out-of-the-box solution without any need of adapting them. In order to find a matching solution to your project you can also get in touch with our support team.

Nevertheless you can find a full sample for the CarConfigurator at qftest-8.0.1/demo/keywords/full_sample_for_carconfig. The sample uses the concept of scenario files as described in section 30.5.

TechnologyNecessary Adjustments
JavaFX
  1. Replace the value awt with fx in the attribute GUI engine on all window components.
  2. Perhaps you need to extend the recorded window components with additional variables.
  3. You need to adapt the procedure startStop.startSUT in order to start your application. Simply copy the created steps from the quickstart wizard.
  4. You might possibly have to create some resolver scripts to tune component recognition.
Java/Swing
  1. Perhaps you need to extend the recorded window components with additional variables.
  2. You need to adapt the procedure startStop.startSUT in order to start your application. Simply copy the created steps from the quickstart wizard.
  3. You might possibly have to create some resolver scripts to tune component recognition.
Java/SWT
  1. Replace the value awt with swt in the attribute GUI engine on all window components.
  2. Perhaps you need to extend the recorded window components with additional variables.
  3. You need to adapt the procedure startStop.startSUT in order to start your application. Simply copy the created steps from the quickstart wizard.
  4. You might possibly have to create some resolver scripts to tune component recognition.
Web
  1. Replace the window component with a Web page node.
  2. As dialogs are already part of the web page you don't need to keep them separated and can create a component within the web page..
  3. You need to adapt the procedure startStop.startSUT in order to start your application. Simply copy the created steps from the quickstart wizard.
  4. You might possibly have to tune component recognition using the CustomWebResolver concept.
Table 30.7:  Necessary adaptions to your SUT
TopTable of contentsPrevious Chapter: 30.6 Custom test case descriptionNext Page: 31 Usage of QF-Test in Docker EnvironmentsChapter Overview: 30 Keyword-driven testing with QF-TestPDF versionLast update: 9/10/2024
Copyright © 1999-2024 Quality First Software GmbH

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".

ACCEPTER
PARAMETRER
REFUSER
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.

Confirmer la sélection

Cookie details