Tutoriel en version vidéo: Nous vous guidons pas à pas à travers QF-Test...
Version 8.0.1 |
There is more than one way to create procedures and insert procedure calls. We will start with the manual one by inserting an (empty) procedure node and moving the respective actions into it. Then we will create the respective procedure call.
It is good to know those basic steps but there is a second more elegant way of creating procedures, which we will explain afterwards.
Okay, let's do it by hand. We will start with creating a procedure node and naming it appropriately.
Figure 3.2: Create a procedure node |
The second step is to fill the procedure with the respective reusable actions.
Figure 3.3: Fill in the procedure content |
The third step is to add a procedure call to the place of the three 'Mouse clicks' you moved.
Figure 3.4: Insert a procedure call |
Figure 3.5: Select a procedure |
In order get a real benefit from the procedure, of course, we also need to replace the content of reset test step in the second test case by the 'reset' procedure call, too.
You can do it the same way as before or use the following alternative steps to create a procedure call:
The test suite should look like this:
Figure 3.6: Test-suite with procedure |
When now executing the test cases the reset will work exactly like it did before. Hence, in the run log you will see the same executed node as before, only preceded by the procedure call.
Last update: 9/10/2024 Copyright © 2002-2024 Quality First Software GmbH |
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.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
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.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.