36.9
Runtime 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 44.6 for details). Which kind of step to use is indicated by the text "Server script name" or "SUT script name" in the documentation of the respective option.

4+Connect via QF-Test agent (System)
Server script name: OPT_PLAY_CONNECT_VIA_AGENT

QF-Test version 4 introduced a new mechanism for connecting to an SUT, based on Java agents. It is far more powerful and flexible than the older mechanisms and even a hard requirement for most current SUTs. Thus it should not be turned off without a very good reason.

Note Without the agent an SUT based on Java 9 or newer will not even start. Besides, the agent is a prerequisite for access to JavaFX, embedded browsers and the full functionality of live unit testing.

4.1+Instrument AWT EventQueue (System)
Server script name: OPT_PLAY_INSTRUMENT_EVENT_QUEUE
Swing

In earlier versions QF-Test replaced the AWT system EventQueue with its own, taking pains to handle custom EventQueues and many other subtle details. Starting with QF-Test 4.1 the default is to instrument the EventQueue class instead which has less impact on the SUT, handles border cases well and is preferable in almost all situations. In case of connection problems, the old mechanism can be used by turning off this option.

Note Instrumenting the AWT EventQueue is only possible with the QF-Test agent.