Version 7.1.5 29.6Custom test case description The previous sections show all samples using Excel files. As already mentioned it's also possible to use different file-types, e.g. XML or CSV files. But you can also think about evaluate the result of a web-service. Therefore, you will need to implement Server-scripts reading the required information like test step name, component names or variables…
Version 7.1.5 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.5 26.4Klaros 26.4.1Introduction Klaros is a test management tool developed and supported by verit Informationssysteme GmbH, Kaiserslautern, Germany. Klaros is available in two kinds of editions, a free community edition and an enterprise edition with an extended set of functionality, individual configuration options and full customer support. The current integration of QF-Test with…
Version 7.1.5 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.5 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.5/ext/testbench/Version_1.1_TestBench_2.3. Please take care to copy all test suites…
Version 7.1.5 28Integration with Robot Framework (Preview) 6.0+Preview Though fully functional, the Robot Framework integration is still considered a preview feature because there are no pre-defined Robot Framework keyword libraries available for QF-Test yet so you have to create your own (which is quite easy, see below). 28.1Introduction Robot Framework is a very popular framework for test…
Version 7.1.5 10The standard library The standard library qfs.qft, a test suite that is part of the QF-Test distribution, contains many useful procedures for a diverse set of tasks. Figure 10.1: Standard library qfs.qft Among others there are procedures for accessing and checking components (AWT, Swing, JavaFX, SWT, Web) in a generic manner, file system and database access, logging messages or…
Version 7.1.5 23Test execution When talking about test execution, there are two aspects to be considered. On one hand you need to run tests while they are developed to check them for proper operation. This situation has already been described in section 4.2. Basically all you have to do to run a test interactively is invoking »Run«-»Start« from the main menu. On the other hand you want to run your…
Version 7.1.5 3.0+26Interaction with Test Management Tools QF-Test contains some pragmatic test management approaches, like creating a test case overview or documenting test cases within QF-Test. In bigger projects it might be necessary to make use of an own dedicated test management system to track the development status of test cases or to link test cases and their results to defects, use cases…
Version 7.1.5 12Unit Tests With Unit Tests, i.e. component tests, you can check the functional units. They explicitly test the functionality of single components. For this reason they are much less complex compared to integration and system tests. The 'Unit test' node executes Unit Tests via the JUnit framework as part of a QF-Test test run. The results are available in the run log as well as in…