JSystem Eclipse plugin for exporting to Wiki

One of the goals of the JSystem is to test the business logic of the SUT.

You can find a lot of documentations about this methodology on this site, so there is no point in repeating it in this blog. I will remind just one thing and this is the system objects approach that allows us to concentrate on business logic. We create system objects as an infrastructure that will be used by testers creating the actual tests and because of that we should make sure that all the functionality that we have created in the system objects, is well documented.

Read more

Lightweight Automation Test Plan Template


This post has been written in order to explain the lightweight template for functional tests document that is the base for the automation process. Test architects can use this template to better integrate with automation experts.

This template is not focused on generic test plan issues (like the document versions) on automation specific issues.

Read more

Activating Junit tests from Command Line

Running Junit tests from command line requires two things.
1) setting your classpath.
2) invoking the junit command.

you’ll need the following elemements in your CLASSPATH:

* JUnit class files
* Your class files, including your JUnit test classes
* Libraries your class files depend on

Windows Example:
set CLASSPATH=%JUNIT_HOME%\junit.jar;c:\myproject\classes;c:\myproject\lib\something.jar

Unix (bash) Example:
export CLASSPATH=$JUNIT_HOME/junit.jar:/myproject/classes:/myproject/lib/something.jar

Read more

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


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; this will allow you to debug test execution.

Read more

GUI drivers

Swing Application


Read more

Network Drivers





Read more

Stations Driver




Read more

Connectivity drivers



Scripting languages

Read more
Page 4 of 512345
Fork me on GitHub