By program level execution we understand
running of automated process(es) from a
custom Java program or a
party Java application. As T-Plan Robot's role is in this
scenario reduced to a Java library, this mode is supported on the level
of Java APIs only and there are no GUI or CLICommand Line Interface features supporting
development of the related Java code. Use a third party tool (an IDE)
such as NetBeans or Eclipse for this purpose.
T-Plan Robot Enterprise supports program level execution through the
ApplicationSupport Java interfaces. The APIApplication Programming Interface allows to create and start either a single
process (effectively simulating a single automatic execution in the GUI
or CLI mode) or an unlimited number of processes (executed as Java
threads) running in
CLI mode (until the system resources are exhausted). Each such a
process seamlessly accepts the same set of options as the CLI and
executes one test script against one test environment
(desktop) at a time.
level execution consists of three steps:
run()method of the runnable (single process scenario) or encapsulate it in a java.lang.
Threadand start it as a thread (multi-threaded scenario).
The following example starts two automated threads. The first one
connects to a VNCVirtual Network Computing (VNC) is a graphical desktop sharing system that uses the RFB protocol to remotely control another computer.
VNC is platform-independent.
Multiple clients may connect to a VNC server at the same time. server running on port 5900 of machine called
testmachine1 and executes the
C:\TestScripts\test1.tpr test script
one connects to a VNC server running on port 5901 of machine
C:\TestScripts\test2.tpr test script. Note that both the threads will
be executed simultaneously and the program will exit when the last
import com.tplan.robot.ApplicationSupport; import com.tplan.robot.AutomatedRunnable; /**
This multi-threaded approach can be also employed in
load testing scenarios. T-Plan Robot can measure the application response time, and it is an excellent engine for the simulation of a number of users accessing the tested application or service
in order to generate load. When this model is combined with another tool for performance
may represent a very cost effective solution.
In addition to supporting the automation of the local desktop, T-Plan Robot utilises the RFB (VNC) technology, and in this mode each thread must automate its own VNC desktop server instance. Such an approach is very efficient with Unix or Linux where a single platform (OS) may run as many VNC servers, as the system resources allow (such as RAM and CPU). This scenario may be exploited for testing of applications running on Unix/Linux and/or for web application testing where the Unix/Linux machine hosts web browser instances. As MS Windows systems may run just one VNC server per OS, load testing on these environments is not so efficient. In these instances it would be better to employ T-Plan Robot ability to automate the local desktop.
T-Plan Robot does provide tools to measure application response time, and produce performance results. As automation is performed on the desktop level, such testing will have an extra added value because it will reflect the true time elapsed between the user request and result. This is in contrast with many other load performance testing tools which typically focus on measuring of one critical phase of the request-response cycle (for example database or web/application server response time). Such results however usually do not correspond with the end user experience, where the time is further on affected by the environment.
|12 December 2014||
Copyright © T-Plan Ltd.