Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexandra Imrie2011-03-15 10:15:41 +0000
committerAlexandra Imrie2011-03-15 10:15:41 +0000
commit345a8043ddad55ca76de07241111c1775d136421 (patch)
tree9aa8ceefff4db1ac5f9ab64671300a034a04ccc1 /org.eclipse.jubula.documentation
parentf5064c7d838240f06b1bd7607ef27bdf1484692e (diff)
downloadorg.eclipse.jubula.core-345a8043ddad55ca76de07241111c1775d136421.tar.gz
org.eclipse.jubula.core-345a8043ddad55ca76de07241111c1775d136421.tar.xz
org.eclipse.jubula.core-345a8043ddad55ca76de07241111c1775d136421.zip
Bugfix for #3519
Diffstat (limited to 'org.eclipse.jubula.documentation')
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/parameters.tex3
1 files changed, 2 insertions, 1 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/parameters.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/parameters.tex
index 878c8b867..f116c54cf 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/parameters.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/parameters.tex
@@ -132,13 +132,14 @@
\item You can either enter a \gdsuite{} to be executed or a \gdjob{}. Only one of these two commands is accepted for the test executor.
+\bxtipp{If you are starting a \gdsuite{}, \app{} will start your \gdaut{} from its configuration if you have entered one. If you are starting a \gdjob{}, you must make sure that the first \gdaut{} you require is already started with the \bxname{autrun} command.}
\item If the \gdaut{} you want to test was started with the \bxname{autrun} command, you must enter an \gdaut{} ID. If your \gdaut{} will be started with an \gdaut{} configuration, then enter the configuration name.
\bxtipp{The test executor also accepts arguments to pass on to the Java Virtual Machine. This means that you can, for example, increase the initial and maximum amount of system memory allocated to the JVM with the parameters \bxshell{-Xms<memory\_size>} and \bxshell{-Xmx<memory\_size>}, respectively. For example, the parameter \bxshell{-Xmx128M} would make a maximum of 128 MB of system memory available to the test executor. When entering the standard parameters for the test executor, you may add \bxshell{-J<JVM\_parameter>} for each JVM parameter you wish to set. For example, \bxshell{-J-Xmx128M}. Multiple parameters, like standard parameters, are separated by spaces. \\
Here is an example of defining mutliple JVM parameters: \bxshell{-J-Xmx128M -JXms128M}.}
\item Using the no run option will check the completeness of the \gdproject{}, test data and the validity of the \gddb{} connection. The \gdagent{} connection is not checked.
\item Once you have entered all the necessary parameters, press \bxkey{enter}.
-\item The client will connect to the \gdagent, connect to the \gddb{}, open the \gdproject{}, start the \gdaut{} and then execute the \gdsuite{} you specified.
+\item The client will connect to the \gdagent, connect to the \gddb{}, open the \gdproject{}, start the \gdaut{} (for \gdsuites{}) or connect to it (for \gdjobs{}) and then execute the \gdsuite{} or \gdjob{} you specified.
\item Once the test has finished, the client will show an exit code.
\begin{itemize}
\item \bxcaption{Exit code: 0} indicates that the test was successful.

Back to the top