is set to the unexpanded 'Client' value of the 'Start SUT client' node through which the SUT was started. Insert recording at current selection (User) Depending on what you are currently working on, it
Version 7.1.4 52.11.1The abstract Node class All classes of QF-Test's pseudo DOM are derived from this class and thus implement the following interface. Its is located in the package de.qfs.apps.qftest.client.web.dom. Node findCommonAncestor(Node node1, Node node2, Node topmost) Get the common parent of two nodes. Parameters node1 The first node. node2 The second node. topmost The topmost node…
Version 7.1.4 34How to start a testing project This chapter talks about the most important aspects that should be considered before you start to use QF-Test widely in your testing project. It mostly raises questions and gives general answers with references to more detailed information. The aim of this chapter is to provide hints about issues which you should take care of in order to make your GUI…
Version 7.1.4 21Data-driven testing Data-driven testing is a very important aspect of test automation. In short, the goal is to run a given test or set of tests multiple times with different sets of input data and expected results. QF-Test has various means to store data or load external data for use in data-driven tests. The most convenient is based on a 'Data driver' node which sets up an…
Version 7.1.4 23.2Executing tests in daemon mode In daemon mode QF-Test listens to RMI connections and provides an interface for remote test execution. This is useful for simplifying test execution in a distributed load-testing scenario (chapter 31), but also for integration with existing test management or test execution tools (chapter 26). NoteGUI tests require an active user session. Chapter…
Version 7.1.4 31Performing GUI-based load tests Video: Load testing 31.1Background and comparison with other techniques In addition to functional and system tests, QF-Test can also be used to perform load tests, stress tests or performance tests. The idea is to test the performance of some server applications by running a number of GUI clients concurrently. Performance is measured by running…
Version 7.1.4 49.2Special support for various web frameworks Modern web applications are generally very interactive and their look and feel is comparable to desktop applications. Behind these applications is a whole zoo of web frameworks that drive them, each with a different focus and unique set of widgets. Such frameworks pose a problem for QF-Test and in fact any automated testing tool for…
Version 7.1.4 52.3The ResolverRegistry Resolvers of all kinds can be implemented via the resolvers module as Jython or Groovy scripts as described in section 52.1. Unless you want to understand how the resolvers module itself works or want to implement a resolver in Java you may skip the following sections. This section describes how to implement a resolver directly by Java classes. However, this…
Version 7.1.4 52.2The webResolvers module 4.2+For most use cases, registering a resolver using the resolvers module as described in the last chapter section 52.1 is the best way to adapt the component recognition of QF-Test. If the custom resolvers are used for a web context and heavily interacting with the browser content directly, the webResolvers module provides an option to run the resolver…
Version 7.1.4 5.4.2Name In case the developers have assigned Component identifiers to a component, QF-Test will recognize this and use it, if suitable, for the attribute 'Name'. If a value for 'Name' was found, it will also be used for generating the 'QF-Test ID' of the component. Examples for this can be found in How to achieve robust component recognition. The value of the 'Name' attribute is…