News

Running JSystem scenario from command line

JSystem scenario is an ant script so running a scenario from command line is as simple as running ant script.

  1. Change directory to the runner installation folder (for example c:\jsystem\runner)
  2. Set ANT_HOME environment parameter
  3. When running on Linux Change ant batch file permission (chmod a+x ./thirdparty/ant/bin/ant)
  4. Make sure an empty ".testPropertiesFile_Empty" file exists under runner root folder

Linux

Read more

Jars order in runner & tests classpath

When the runner starts it collects jars from the following folders in the following order:

1. runner/thirdparty/ant/lib
2. runner/thirdparty/commonLib
3. runner/thirdparty/lib
4. runner/customer_lib
5 .runner/lib
6. {automationProject}/lib

The way to affect the order of jars in the classpath is to move them between the folders above.
(for example jar in runner/customer_lib will be precede in the classpath jar in runner/lib folder)

Read more

Remote debugging jsystem tests

To debug the runner/test running on a remote machine do the following:

1. To debug the runner, add the following java property to runner activation command:
-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y
2. To debug a test Add the above line to the property test.vm.params in the jsystem.properties; this will allow you to debug test execution.

Read more

GUI drivers

Swing Application

Selenium

Read more

Network Drivers

JWinpCap

IPerf

Wireshark

tcpdump

Read more

Stations Driver

Stations

embeddedCatalina

FileTransfer

Read more

Connectivity drivers

CLI

SNMP

Scripting languages

Read more

JSystem Drivers

Read more

Tips and Tricks

a book, main page

Read more
Page 4 of 41234
Fork me on GitHub