As stated in the previous section business-related procedures represent a real business workflow in your application.
You can find a sample at
The respective test-plan can be found at
Please take care to copy the demo folder to a project-related folder first and modify them there.
The sample shows the "Create vehicle" test case of the QF-Test CarConfigurator. It consists of following test steps:
Let's take a look at the Excel file now:
|Figure 29.1: Excel file business-related keywords|
As QF-Test can read excel files row by row, we have decided to go for that excel structure. Reading that file follows the data-driven concept (see section 40.4). It's also possible to use another structure of the excel file, but then we lose the advantage of using the QF-Test functionality directly without any scripts or if-conditions.
In the first row we find the values
That row will be interpreted as variable names by QF-Test. Every subsequent row will then contain respective values for those variables.
This mechanism allows QF-Test to walk through that Excel file in order to execute the planned test steps.
Now let's take a look at the test suite
The test suite looks like this:
|Figure 29.2: Test suite business-related keywords|
|Table 29.5: Structure of SimpleKeywords.qft|
All required procedures are implemented in the package
business. In order to allow a simple variable definition any steps in Excel use the variables
value2. Every procedure maps those generic names to the specific parameters of the procedure itself.
|Figure 29.3: Procedure fillDialog|
This concept requires that any used keyword has to be implemented in QF-Test already before using it. If your steps require more than two parameters you need to extend the excel file with more columns. In addition you need one test case node in QF-Test per test case in Excel. You can make this more flexible, see section 29.5.
|Last update: 5/31/2023|
Copyright © 1999-2023 Quality First Software GmbH