Manual
 

TopTable of contentsPrevious Chapter: 30.4 Behavior-driven testing (BDT)Next Page: 30.6 Custom test case descriptionNext Chapter: 30.6 Custom test case descriptionChapter Overview: 30 Keyword-driven testing with QF-TestPDF versionQF-Test
Version 8.0.1

Scenario 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 at qftest-8.0.1/demo/keywords/generic_with_scenario/Keywords_With_Generics.qft. The scenario itself can be found in qftest-8.0.1/demo/keywords/generic_with_scenario/scenario.xlsx. All used test cases are described in a separate excel file, see qftest-8.0.1/demo/keywords/generic_with_scenario/keywords-generic-testcases.xlsx. Please take care to copy the demo folder to a project-related folder first and modify them there.

The provided scenario consists of two test cases using the concept of generic procedures and components (see section 30.3). You can use any other approach, if you want.

Let's take a look at the scenario Excel file.

Figure 30.8:  Excel file as scenario file

The worksheet "Scenario" contains a column "testcase". This value will be used as variable later. Each subsequent row represents a test case name. Those test cases correspond with the worksheets in keywords-generic-testcases.xlsx. The worksheets "tc_createvehicle" and "tc_createvehicle_cheap" contain the respective test case description.

How does the test suite look like?

Figure 30.9:  Test suite scenario file
NodePurpose
Test set "Generic samples with scenario" Represents the container node for the test execution. This node could be omitted theoretically.
Dependency reference dependencies.sutStarted The concept of dependencies allows QF-Test to manage the starting and stopping process of your application in an intelligent way. Dependencies can contain a strategy in case of any unexpected behavior during test run. See section 41.3 for details.
Data driver "scenario" Here we read the required test cases to execute.
Excel file "test cases" Points to the scenario excel file.
Test case "Generic test case" This node represents the implemented test case.
Teststep "Walk through test steps" This node is required to read the test steps from the excel file with a data driver node.
Data driver "steps from excel" A data driver reads the content of the Excel file describing the test case row by row.
Excel file "steps from excel" Points to the Excel file describing the test case.
Test step "Generic test step" This node will be filled with the current test step name from Excel during execution. This approach will create a readable report.
Call procedure "generic.$(teststep)" Here the respective procedure defined in Excel is called. The variable teststep will be filled with the test data of Excel because of the data driver mechanism.
Table 30.6:  Structure of Keywords_With_Generics.qft
TopTable of contentsPrevious Chapter: 30.4 Behavior-driven testing (BDT)Next Page: 30.6 Custom test case descriptionNext Chapter: 30.6 Custom test case descriptionChapter Overview: 30 Keyword-driven testing with QF-TestPDF versionLast update: 9/10/2024
Copyright © 1999-2024 Quality First Software GmbH

We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months. A revocation, so-called opt-out, is possible at any time on our privacy page.

ACCEPT
CONFIGURE
DECLINE
Cookie configuration

1. Functional cookies

We use functional cookies to ensure the basic functionality of the website.

2. Performance and statistic cookies

We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.

Confirm selection

Cookie details