Version 7.1.4 47.5Quoting and escaping special characters A common problem for most complex systems is the treatment of characters with a special meaning. A typical example are blanks in filenames. To specify such filenames on the command line, they need to be protected either by using double quotes or by escaping the blanks with a backslash character ('\'). Since QF-Test makes use of special…
Version 7.1.4 46.1Weighting of recognition features for recorded components When searching for a component, QF-Test calculates the probability with which each component in the SUT corresponds to the searched component. The component with the highest probability is then used, as long as that this probability is above a freely configurable threshold. First, the probabilities of the windows in the…
Version 7.1.4 47.3Regular expressions The regular expressions that you can use in the search and replace dialogs and in places like the 'Feature' attributes, the 'Primary index' of an 'Item' node or in checks all use standard Java regexp syntax. Before QF-Test version 3.1 the default was the GNU regexp package (see also appendix F). It can still be activated via the option Use old-style GNU…
Version 7.1.4 SWT45.2SWT instrumentation Some special setup is required for testing SWT based applications with QF-Test/swt. Because SWT was not written with testability in mind, applications need to be run with a few slightly modified SWT classes in which we have added the necessary hooks for event filtering and component tracking to enable testing. The changes are transparent so that the…
Version 7.1.4 3.1+52.7Test run listeners Once registered with the current run context via rc.addTestRunListener, an implementation of the TestRunListener interface will get notified whenever test execution enters or exits a node and when a problem occurs. An illustrative example is provided in the test suite TestRunListener.qft, located in the directory demo/runlistener in your QF-Test…
Version 7.1.4 50.2Example Please find the sample test suites in the subdirectories demo/carconfigWpf and demo/carconfigForms of the QF-Test installation directory. 50.2.1Starting the application The sample test suites use the dependency SUT_started in the package qfs.autowin.dependencies of the standard library to start the demo application. The node Execute shell command actually starts the demo.…
Version 7.1.4 49.3Browser connection mode QF-Test has three different modes to gain access to a browser. This section describes these modes in details. 4.1+ Given that the QF-Driver approach using embedding is not maintained anymore by some browser vendors or is not supported at all, a new mechanism was implemented for QF-Test 4.1 to support future browsers and browser versions. This mechanism…
Version 7.1.4 4.1+52.12WebDriver SUT API The WebDriverConnection SUT API provides classes and interfaces to enable using Selenium WebDriver Java API inside a 'SUT script'. With this kind of bridge you can use your existing Selenium WebDriver scripts inside a 'SUT script' of QF-Test. You can even combine the Pseudo DOM API (section 52.11) with Selenium WebDriver based scripts. NoteThis API is only…
Version 7.1.4 5.0+52.13Windows Control API The elments of native Windows applications are represented during a test by Java objects of the class WinControl. This class provides several public methods, e.g. to develop custom resolvers. 52.13.1The WinControl class Following is a list of the methods of the WinControl class in alphabetical order. WinControl getAncestorByUiaType(String typeName)…
Version 7.1.4 5.4.1Class The class of a component is a very important attribute as it describes the type of the recorded component. Once QF-Test records a button, it will only look for a button on replay, not for a table or a tree. Thus the component class conveniently serves to partition the components of a GUI. This improves performance and reliability of component recognition, but also helps…