Version 7.1.5 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.5 7.0+39.4SmartID und qfs:label The following settings define details for capture and replay of SmartIDs and qfs:label* variants. Please see section 5.6 and subsection 5.4.4.1 for details. Figure 39.30: SmartID und qfs:label-Optionen 6.0+SmartID recording (System) Server (automatically forwarded to SUT) script name: OPT_RECORD_SMARTID If this option is active, SmartIDs will be…
Version 7.1.5 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.5 40.1The test suite and its structure There are more than 60 different kinds of nodes for a test suite which are all listed in this chapter. Each node type has a unique set of features. The attributes of a node are displayed and edited in the detail view of the editor. The restrictions that apply to each attribute are listed as well as whether it supports variable expansion (see…
Version 7.1.5 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.5 49.1Improving component recognition with a CustomWebResolver Video: 'CustomWebResolver in QF-Test'. HTML is a very flexible language for describing the content of web pages. But unfortunately there are no real standards with regard to components which should be used to draw a button, a text field or a table showing data. As a result nearly every framework implements its own way of…
Version 7.1.5 60Doctags Besides node attributes QF-Test also supports doctags to influence the behavior of nodes during test execution or for report generation. Doctags can be specified in the 'Comment' attribute of a node in the form @teststep or @noreport node. They must be placed after the general description of the node. 60.1Doctags for reporting and documentation Doctags used for formatting…
Version 7.1.5 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…
Version 7.1.5 4.0+59Generic classes QF-Test abstract recorded class from the framework specific classes in order to get classes of common use. Those classes are called generic classes. This concept provides a better readability and clearer understanding of components. Furthermore already created tests can be re-used once the target technology is switched or if you want to maintain tests in various…
Version 7.1.5 55The ManualStepDialog The ManualStepDialog is a Java class delivered by QF-Test. If you want to make use of this dialog for your own tests, please see following sample script and API specification.
from de.qfs.apps.qftest import ManualStepDialog
#create the dialog and show it immediately
manualDialog = ManualStepDialog(None, "New Test Case Title", \
…