Version 7.1.3 33Introduction This part of the manual describes best practices based on lessons learned from several customer projects and user feedback. The concepts described should assist you in finding the best strategy for using QF-Test in your projects. Note QF-Test is a very generic tool. The hints and experiences described here are just suggestions from our point of view, which we hope will…
Version 7.1.3 27Integration with Development Tools Automating GUI testing is just one part of the development cycle. Requirements like automating the compilation or build process, running tests, creating documentation or providing a deliverable package led on to a variety of different development tools like IDEs (e.g. Eclipse) or build tools (e.g. make, ant, maven) or so called continuous…
Version 7.1.3 B.9QF-Test version 4 B.9.1QF-Test version 4.7 B.9.2QF-Test version 4.6 B.9.3QF-Test version 4.5 B.9.4QF-Test version 4.4 B.9.5QF-Test version 4.3 B.9.6QF-Test version 4.2 B.9.7QF-Test version 4.1 B.9.8QF-Test version 4.0 Last update: 4/23/2024 Copyright © 1999-2024 Quality First Software GmbH
Version 7.1.3 40Elements of a test suite 40.1The test suite and its structure 40.2Test and Sequence nodes 40.3Dependencies 40.4Data driver 40.5Procedures 40.6Control structures 40.7Processes 40.8Events 40.9Checks 40.10Queries 40.11Miscellaneous 40.12HTTP Requests 40.13Windows, Components and Items 40.14Deprecated nodes Last update: 4/23/2024 Copyright © 1999-2024 Quality First Software GmbH
passwords (System) QF-Test can store encrypted passwords in the 'Text' attribute of a 'Text input' node for a password field or the 'Detail' attribute of a 'Selection' used for a login dialog in a web SUT [...] as hierarchic sub-items it is possible to select a node that is not visible because one of its ancestral nodes is not expanded. If this option is set, all ancestors of the node will be…
Version 7.1.3 39.11Runtime only Some options of a more technical nature are not available via the user interface, especially if they are useful only in very specific cases and will do more harm than good in general. As mentioned in the introduction to this chapter, options can be set in 'Server script' or 'SUT script' nodes via rc.setOption(Options.<OPTION_NAME>, <value>) (see section 48.5 for…
Version 7.1.3 39.10Variables The following options pertain to variable binding. Figure 39.41: Variable options 3.0+When binding variables, expand values immediately (System) Server script name: OPT_VARIABLE_IMMEDIATE_BINDING When a set of variable bindings is pushed onto a variable stack, any additional variable references in the values of these variables can either be expanded immediately, or…
Version 7.1.3 51Controlling and testing native MacOS applications At the moment QF-Test primarily supports functional testing of Java and Web applications. We are working on a comparable module for testing native MacOS applications with equivalent processes and features. The module described in this chapter provides a temporary solution when simple control of native MacOS applications is required…
Version 7.1.3 53Daemon mode !!! Warning !!! Anybody with access to the QF-Test daemon can start any program on the machine running the daemon with the rights of the user account that the daemon is running under, so access should be granted only to trusted users. If you are not running the daemon in a secure environment where every user is trusted or if you are creating your own library to connect…
Version 7.1.3 52Extension APIs QF-Test provides some extension APIs that let you extend its functionality. The interfaces can conveniently be implemented in Jython, Groovy or or Java. In the latter case, the compiled classes should be put in a jar file and placed in the plugin directory (see section 48.2) so Jython or Groovy can be used to glue things together. 52.1The resolvers module 52.2The…