Child pages
  • Setup (Automated) UI Testing for the Smart Client Using QFTest

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Download QF-Test: download page
  • Licensing : in the qftest install folder (../qfs/qftest/) copy these files: license, license.old, license.new
  • On first startup of QF-Test and/or the System Under Test (SUT) via QF-Test you might

...

  • might get a security warning from the Windows firewall asking whether to block Java or not.

...

  •  As QF-Test communicates with the SUT by means of network protocols, this

...

  • must not be blocked by the local firewall in order to allow automated testing. 

JRE instrumentation

...

 

  • make sure JRE is installed; 
  • instrumentation of the JRE on which the SUT will run is now the primary method of providing a way for QF-Test to interact with the SUT. Normally you don't need to instrument standard JREs because QF-Test passes the same information to the SUT's JRE via environment variables. However, for special cases instrumentation may be required anyway
    • in main menu select – "Extras" -> "Manage Instrumentation" -> "Instrument" (if the path is not shown, click "Search" first and point to the jre install folder)
    • the State changes to: "Instrumentation current"

...

  • Install with default settings (Servoy Developer)

...

  • _
    Warning

    If Servoy is installed on Windows Xp, make sure that Microsoft Microsoft Visual C++ 2008 Redistributable Package (x86) is preinstalled – otherwise Postgres won't be installed correctly

    _
  • Create/export the solution for testing - System Under Test (SUT)
  • Start AppServer and import the SUT

...

  • Next step give a proper client name: for ex: "svy_sample" - This name serves as central reference to identify your client
  • Next step: "Start automatically" is checked – QF-Test will launch SmartClient
  • Wait for the client to launch
  • Save the script (File-Save) with a desired name

...