Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZeb Ford-Reitz2011-03-01 11:07:33 +0000
committerZeb Ford-Reitz2011-03-01 11:07:33 +0000
commit526d4a272d0ff9a4d27274159f810059061bb327 (patch)
tree2aed41458184f2a633cb8d293348c81cd5ded9a6 /org.eclipse.jubula.documentation
parent2983f9c915fc1eba645dcf45274f8897651fe8fb (diff)
parent28ccc178da246cac8e64fa88bb0512c9c84d7ba7 (diff)
downloadorg.eclipse.jubula.core-526d4a272d0ff9a4d27274159f810059061bb327.tar.gz
org.eclipse.jubula.core-526d4a272d0ff9a4d27274159f810059061bb327.tar.xz
org.eclipse.jubula.core-526d4a272d0ff9a4d27274159f810059061bb327.zip
Merge branch 'master' of ssh://gatekeeper.bredex.de:2405/gitroot/jubula/org.eclipse.jubula.core
Diffstat (limited to 'org.eclipse.jubula.documentation')
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/CONTENT.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/configureaut.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/defineaut.tex8
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/gdrun.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/start.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Adapt/adapt.tex38
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/CONTENT.tex11
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/ant.tex93
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/configfile.tex11
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/embedded.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/intro.tex10
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/issues.tex30
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/parameters.tex137
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/starting.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/CONTENT.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/hierarchy.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/intro.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/merge.tex3
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/new.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/reassigning.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/rename.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Editors/CONTENT.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/CONTENT.tex3
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/add.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/CONTENT.tex1
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/changeaut.tex3
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/intro.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Manual/create.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/CONTENT.tex49
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/GenerateDialog.pngbin18039 -> 0 bytes
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/ModelError.pngbin12729 -> 0 bytes
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/Model_ReusedTCs.pngbin18120 -> 0 bytes
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/add.tex61
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/appearance.tex8
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createmodel.tex16
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createproject.tex18
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/generate.tex43
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/import.tex27
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/models.tex10
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/options.tex15
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/validate.tex20
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/editor.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/openOME.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/robust.tex7
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/showwhereused.tex10
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/CONTENT.tex29
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/appearance.tex28
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/dbprefs.tex27
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/diagramprefs.tex69
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/editor.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/gdprefs.tex16
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/keys.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/obsprefsweb.tex12
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/omprefs.tex5
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/serverConfigPrefPage.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/testresultprefs.tex7
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/CONTENT.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/entering.tex47
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observejava.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observeweb.tex38
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/startobs.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/tips.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex8
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Searching/searchdialog.tex16
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/AUTstop.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/TSstop.tex19
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/application.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testcases/edit.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/CONTENT.tex8
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/central.tex7
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/concatenate.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/datasets.tex3
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/excel.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/overwritedata.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/special.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/variables.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/CONTENT.tex10
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/TSstart.tex5
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/pause.tex17
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/preparing.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/speed.tex11
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/startaut.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/CONTENT.tex11
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/external.tex5
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/generatebirt.tex32
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/ownbirt.tex34
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/summary.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/xmlreport.tex20
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/editing.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/specify.tex13
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/CONTENT.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/TSeditorUse.tex1
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/edit.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/CONTENT.tex12
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/aut.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/failedsuite.tex7
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/intro.tex8
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/logging.tex30
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/mail.tex3
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/servererrors.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/intro.tex38
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/perspectives.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/views.tex8
103 files changed, 278 insertions, 1086 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/CONTENT.tex
index df3ae76f8..92ea17dc9 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/CONTENT.tex
@@ -16,5 +16,5 @@
\subsection{Starting \gdauts{} with the \bxname{autrun} command}
\gdhelpid{autSettingWizardPagePageContextId}{Defining an AUT}
-\label{gdrun}
+\label{autrun}
\input{Tasks/AUTs/gdrun}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/configureaut.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/configureaut.tex
index 3eeed94ab..1820a6139 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/configureaut.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/configureaut.tex
@@ -36,7 +36,7 @@ Once you have created a \gdproject{} \bxpref{newproject} and defined an \gdaut{}
The details in the \gdaut{} configuration tell \app{} how to start the \gdaut{}, e.g. on which machine.
An \gdaut{} can have multiple configurations (for example, for local and remote testing).
-\bxtipp{If you want to start your \gdaut{} yourself, and have \app{} connect to it, then use the \bxname{autrun} command to start the \gdaut{} \bxpref{gdrun}. In this case, you do not need to create an \gdaut{} configuration.}
+\bxtipp{If you want to start your \gdaut{} yourself, and have \app{} connect to it, then use the \bxname{autrun} command to start the \gdaut{} \bxpref{autrun}. In this case, you do not need to create an \gdaut{} configuration.}
The \gdaut{} configuration dialog has three different levels of detail: basic, advanced and expert.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/defineaut.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/defineaut.tex
index 0470f89b3..cdeb64784 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/defineaut.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/defineaut.tex
@@ -32,7 +32,7 @@
Once you have created a \gdproject{}, you can define (and edit) \gdauts{}.
You can define a new \gdaut{} straight after creating the \gdproject{} in the \gdproject{} wizard or you can do it later on via the \gdproject{} properties \bxpref{projectproperties}.
-\bxtipp{If you will be starting your \gdaut{} with the \bxname{autrun} command \bxpref{gdrun}, then you can automatically define your \gdaut{} \bxpref{createAUTDef}}
+\bxtipp{If you will be starting your \gdaut{} with the \bxname{autrun} command \bxpref{autrun}, then you can automatically define your \gdaut{} \bxpref{createAUTDef}}
The \gdaut{} dialog (\bxfigref{autdialog}) appears when you define or edit an \gdaut{}.
@@ -49,9 +49,9 @@ The \gdaut{} dialog (\bxfigref{autdialog}) appears when you define or edit an \g
\item Enter a meaningful and unique \gdaut{} name. This is used to easily identify the \gdaut{} later.
\item Select the toolkit the \gdaut{} uses from the combo box.
\item If you choose RCP, decide whether or not \app{} should generate names for components in the \gdaut{} which have not been named by your developers \bxpref{RCPgenerate}. We recommend leaving this option checked, as it increases the robustness of your tests.
-\item If you will be starting this \gdaut{} using the \bxname{autrun} command \bxpref{gdrun}, or if the \gdaut{} will be launched from another \gdaut{} during the test \bxpref{TasksLenientTest}, then enter the ID(s) for these \gdauts{} here.
+\item If you will be starting this \gdaut{} using the \bxname{autrun} command \bxpref{autrun}, or if the \gdaut{} will be launched from another \gdaut{} during the test \bxpref{TasksLenientTest}, then enter the ID(s) for these \gdauts{} here.
\textbf{IDs for \gdauts{} started by the \bxname{autrun} command}\\
-Enter the \gdaut{} IDs you will use for any \gdauts{} started by the \bxname{autrun} command (the \gdaut{} ID for the \gdaut{} is given as a parameter in the \bxname{autrun} command \bxpref{gdrun}.
+Enter the \gdaut{} IDs you will use for any \gdauts{} started by the \bxname{autrun} command (the \gdaut{} ID for the \gdaut{} is given as a parameter in the \bxname{autrun} command \bxpref{autrun}.
\textbf{IDs for \gdauts{} launched by other \gdauts{}}\\
The \gdaut{} ID will take a specific form \bxpref{TasksLenientTest} and must be defined as such in the \gdaut{} definition.
@@ -66,6 +66,6 @@ The languages you select are the languages the \gdaut{} can be started in. You
\item If you want to start this \gdaut{} via \app{}, you can do so in the \gdproject{} properties \bxpref{configuringaut}.
\end{enumerate}
-If you do not require an \gdaut{} configuration, because you will be starting the \gdaut{} using the \bxname{autrun} command \bxpref{gdrun}, then you do not need to create an \gdaut{} configuration.
+If you do not require an \gdaut{} configuration, because you will be starting the \gdaut{} using the \bxname{autrun} command \bxpref{autrun}, then you do not need to create an \gdaut{} configuration.
\clearpage
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/gdrun.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/gdrun.tex
index 453918a51..89ca96de8 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/gdrun.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/gdrun.tex
@@ -21,7 +21,7 @@ To use the \bxname{autrun} command:
\item Ensure that the \gdagent{} is installed on the machine where you will be starting the \gdaut{}.
\item Start your \gdaut{} via the command line by entering \bxshell{autrun.exe} then the following parameters:
\begin{table}[h]
-\label{gdrunparams}
+\label{autrunparams}
\centering
\begin{tabular}{|l|l|}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/start.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/start.tex
index 95dcae167..0000d9b70 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/start.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/AUTs/start.tex
@@ -2,5 +2,5 @@
\begin{description}
\item [Via an \gdaut{} configuration:]{This option means that you create an \gdaut{} configuration in your \gdproject{}, and the \gdaut{} is started by \app{} \bxpref{configuringaut}.}
-\item [Using the \bxname{autrun} command:]{This option lets you start an \gdaut{} without creating a configuration. Certain start parameters are required for the \gdaut{} so that \app{} can locate it \bxpref{gdrun}.}
+\item [Using the \bxname{autrun} command:]{This option lets you start an \gdaut{} without creating a configuration. Certain start parameters are required for the \gdaut{} so that \app{} can locate it \bxpref{autrun}.}
\end{description}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Adapt/adapt.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Adapt/adapt.tex
index 081fcd136..4b56fa76f 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Adapt/adapt.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Adapt/adapt.tex
@@ -17,22 +17,6 @@
\index{Specification!Perspective}
You can individualize the \app{} user interface in various ways.
-\subsection{Color-coding the user interface}
-%appearancehelpid
-\begin{enumerate}
-\item To change the color-coding on the borders of related browsers, views and
-editors, select:\\
-\bxmenu{Window}{Preferences}{} \\
-and select \bxcaption{Appearance} from the list on the left-hand side.
-\item Use the \bxcaption{color} buttons to select a colors for your client.
-
-\item Choosing a color for \bxcaption{Specification} will make the borders of the \gdtestcasebrowser{}, \gdtestcaseeditor{} and their three support views all have the color you choose.
-
-\item By choosing a color for \bxcaption{Execution}, the borders of the \gdtestsuitebrowser{}, \gdtestsuiteeditor{} and their three support views will all be in the color you choose.
-
-\item You can also check the box to switch off the color-coding option.
-\end{enumerate}
-
\subsection{Moving Browsers, Views and Editors}
You can move items in the user interface in two ways:
@@ -61,24 +45,6 @@ appears as a blue line which can be dragged and dropped.
the context-sensitive menu of the tab area.
\end{itemize}
-%\subsection{Ordering items in browsers}
-%\gdhelpid{testExecViewContextId}{Test Suite Browser}
-%\gdhelpid{testSpecificationViewContextId}{Test Case Browser}
-%% To alter the way the items in a view or browser are shown:
-%% \begin{itemize}
-%% \item Select the icon in the right-hand corner of a view or browser
-%% to entirely collapse the trees.
-%% \gdmarpar{../../../share/PS/collapse}{collapse tree}
-%% \item Right-click on a node in the browser and select \bxcaption{expand} to
-%% expand that node alone.
-%% \item To arrange items alphabetically, activate the leftmost icon
-%% in the right-hand
-%% corner of the view or browser.
-%% To reorder the icons as they were previously, click
-%% the icon again.
-%% \gdmarpar{../../../share/PS/sort}{ arrange/reorder}
-%% \end{itemize}
-
\subsection{Restoring user interface defaults}
\begin{enumerate}
\item You can restore the default perspective at any time: \\
@@ -101,10 +67,10 @@ corner of the current perspective to toggle between perspectives.
\end{enumerate}
\subsubsection{Automatically changing perspective}
-%\gdhelpid{prefPageBasicContextId}{GUIdancer Preferences}
+
By selecting:\\
\bxmenu{Window}{Preferences}{},\\
-you can choose to automatically change to the Execution perspective when test execution starts,
+you can choose to automatically change to the \execpersp{} when test execution starts,
or to be asked each time a \gdsuite{} is started.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/CONTENT.tex
index 0aea5743a..7f0ac5960 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/CONTENT.tex
@@ -18,20 +18,15 @@
\input{Tasks/Commandline/intro}
-\subsection[Starting]{Starting the command line client}
+\subsection[Starting]{Starting the test executor}
\input{Tasks/Commandline/starting}
-\subsection[Parameters]{Parameters for the command line client}
+\subsection[Parameters]{Parameters for the test executor}
\input{Tasks/Commandline/parameters}
-\subsection{Using the command line client with the embedded \gddb{}}
+\subsection{Using the test executor with the embedded \gddb{}}
\input{Tasks/Commandline/embedded}
\subsection[Configuration Files]{Using a configuration file}
\input{Tasks/Commandline/configfile}
-%% \subsection[Ant Tasks]{Performing Tests as an Ant Task}
-%% \input{Tasks/Commandline/ant}
-
-\subsection[Issues]{Issues with using the command line client}
-\input{Tasks/Commandline/issues}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/ant.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/ant.tex
deleted file mode 100644
index fee138eee..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/ant.tex
+++ /dev/null
@@ -1,93 +0,0 @@
-\app{} tests can be performed as part of an \bxname{Apache Ant} build
-process. If you are already familiar with ant tasks, integrating \app{}
-tests into your production process is straightforward. The following is a snippet of an example \bxshell{build.xml}
-file:
-
-\footnotesize
-\begin{verbatim}
-<project name="GDTestProject" basedir="[install directory]">
- <taskdef name="guidancer"
- classname="com.bredexsw.guidancer.client.cmd.ClientTask">
- <classpath>
- <fileset dir="${basedir}">
- <include name="guidancer/ClientCmd.jar" />
- </fileset>
- </classpath>
- </taskdef>
- <target name="test" depends="">
- <guidancer
- project="MyProject"
- server="gdserver.example.com"
- port="5556"
- dburl="jdbc:oracle:thin:@db.example.com:1521:dbname"
- dbuser="mydblogin"
- dbpw="mydbpassword"
- testsuites="MyTestSuite1,MyTestSuite2"
- autconfig="MyAUTConfig"
- language="en_US"
- resultdir="."
- />
- </target>
-</project>
-\end{verbatim}
-\normalsize
-
-The above \bxshell{basedir} attribute of the \bxshell{project} element should be set to the \app{}
-installation directory, i.e.
-\bxshell{C:$\backslash$Program Files$\backslash$guidancer}. A relative
-path can also be used, as seen above. The contents of the
-\bxshell{taskdef} section should be left as is. These set up \app{}'s
-running environment and include necessary libraries and resource files.
-
-\bxwarn{Changing the \bxshell{taskdef} settings may prevent your tests
-from being able to run!}
-
-The \bxshell{target} definition needs to be adjusted to your
-environment. The \bxshell{name} property within the \bxshell{target}
-tag can be set to your desired name for test execution. The properties
-enclosed in the \bxshell{guidancer} tag should be set as follows:
-
-\begin{description}
- \item{\textbf{project}} The name of the \gdproject{} containing the
- \gdsuites{} that you wish to run.
- \item{\textbf{version}} The version of the \gdproject{} containing the
- \gdsuites{} that you wish to run.
- \item{\textbf{autconfig}} The name of the \gdaut{} configuration, as entered
- in your \gdproject. If your \gdproject{} contains only one \gdaut,
- this option may also be omitted.
- \item{\textbf{server}} The name of the computer that \gdagent{} is running
- on.
- \item{\textbf{port}} The port number that the \gdagent{} is running on.
- \item{\textbf{dburl}} The JDBC URL of the \gddb{} containing your \app{}
- \gdprojects. This option may be omitted, in which case the \gddb{}
- configured using \app{}'s configuration tool will be used.
- \item{\textbf{dbuser}} The login name to the \gddb. When using the \gdintdb{} (default installation), this should be set to ''sa''.
- \item{\textbf{dbpw}} The password to login to the \gddb. When using the
- \gdintdb{} (default installation), this should left blank
- (e.g. \verb+dbpw=+'''' ).
- \item{\textbf{testsuites}} The names of the \gdsuites{} that you wish to
- be executed. This option may be omitted, but only if your
- \gdproject{} only contains a single \gdsuite{}.
- \item{\textbf{language}} The language that the test(s) are to be executed
- in. If this property is omitted, the default language for your
- \gdproject{} will be used.
- \item{\textbf{datadir}} The path to the directory where external data are stored.
-\item{\textbf{resultsdir}} The path to the directory where the test results should be stored.
-\end{description}
-
-Once your \bxname{Ant} task and target are set up, your test can be
-executed from the command line, using the name given to your target:
-
-\bxshell{ant test}
-
-or called as part of a build script:
-
-\begin{verbatim}
-<project name="MyProject">
-...
-<ant antfile="<location_of_my_gd_build_script>/<name_of_my_gd_ant_file>"
- target="<mytargetname>"
- inheritAll="false"/>
-...
-</project>
-\end{verbatim}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/configfile.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/configfile.tex
index 9b86f9daa..763044171 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/configfile.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/configfile.tex
@@ -15,9 +15,9 @@
%% % ----------------------------------------------------------------------
%% \end{document}
-\index{Command Line Client}
+\index{Test Executor}
\begin{enumerate}
-\item You can also enter command line client details in an XML configuration file.
+\item You can also enter test executor parameters in an XML configuration file.
\item This saves you typing in the same details each time you start a test.
\item To enter the configuration file path, enter the following command:\\
\bxshell{-c <path to file>}
@@ -36,10 +36,11 @@ For example:
<project>ExampleProject</project>
<version>1.0</version>
<autconfig>local configuration</autconfig>
+ OR
<autid>Adder</autid>
<dbscheme>Embedded</dbscheme>
- <dbuser>joebloggs</dbuser>
- <dbpw>mypassword</dbpw>
+ <dbuser></dbuser>
+ <dbpw></dbpw>
<server>localhost</server>
<port>60000</port>
<language>EN_US</language>
@@ -57,5 +58,5 @@ For example:
\bxtipp{Java Virtual Machine parameters can only be entered in the command line interface. They cannot be entered in the configuration file.}
\end{enumerate}
\item A template configuration file was installed with \app{}. It can be found under:\\
-\bxname{GDInstallationDir/examples/scripts}
+\bxname{InstallationDirectory/examples/scripts}
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/embedded.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/embedded.tex
index 172f45a1b..cc7a81ff2 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/embedded.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/embedded.tex
@@ -1,9 +1,9 @@
-\index{Command Line Client}
+\index{Test Executor}
-If you are using the default embedded \gddb{}, you will need to enter the following information as command line parameters:
+If you are using the default embedded \gddb{}, you will need to enter the following information as parameters:
\begin{description}
\item[-dbscheme]{Embedded}
-\item[-dbuser]{sa}
+\item[-dbuser]{<empty>}
\item[-dbpw]{<empty>}
\end{description}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/intro.tex
index 2fe5b66c8..8c07abca3 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/intro.tex
@@ -16,12 +16,6 @@
%% \end{document}
-You can also run tests using the command line client. From the command line interface, you can select and start multiple \gdsuites{} from a \gdproject{}.
+You can also run tests using the test executor. From the command line interface, you can select and start tests.
-%You can also write an ANT file to execute various \gdsuites{} from different \gdprojects{}.
-
-\bxtipp{As with any test, it is a good idea to make sure that the first
- action is a \bxcaption{wait for component} action, which waits for
- the first component you want to test. The timeout should be
- relatively long.
- This gives your \gdaut{} the chance to start up before the test starts.}
+\bxtipp{It is especially important to ensure that your test contains a suitable startup module to wait for the \gdaut{}, perform the login if necessary and reset the \gdaut{} to a defined state when you are running tests from the command line. }
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/issues.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/issues.tex
deleted file mode 100644
index 17e07f1b8..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/issues.tex
+++ /dev/null
@@ -1,30 +0,0 @@
-
-The following describes aspects concerning the Command Line Client
-which should be considered when specifying your tests.
-
-\subsubsection{Batch vs. Interactive}
-
-Specifying tests with the \app{} GUI is necessarily an \emph{interactive}
-process, as the user is actively working with the program, providing
-input and responding to feedback.
-
-Test execution, however, can be
-carried out either in an interactive or a \emph{batch}
-process. \app{} provides some test actions that are meant for interactive
-use, such as the \bxcaption{Pause} action for the
-\bxcaption{Application} component. This action pauses test
-execution, waiting for the user command to either continue or stop
-test execution.
-
-However, when tests are intended for \emph{batch} execution, as is the
-case when using the Command Line Client, such
-actions lose their meaning, as no user is expected to be present to
-respond. \app{} thus ignores interactive actions in this case.
-
-\bxtipp{We recommend starting tests with a \bxname{wait for component} action. This eliminates timing problems with batch runs. }
-
-\subsubsection{When Errors Occur}
-
-If an error occurs in a \gdsuite{}, such that it can no longer be
-executed to the finish, the Command Line Client will automatically
-begin testing with the next specified \gdsuite{}, if one exists.
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 8500f13e6..ec4b82b0d 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
@@ -15,10 +15,10 @@
%% % ----------------------------------------------------------------------
%% \end{document}
-\index{Command Line Client}
+\index{Test Executor}
\begin{enumerate}
-\item Once you have browsed to the \app{} installation directory and entered \bxshell{GUIdancerCMD}, you can enter the parameters for the test execution.
-\item The command line client has various parameters \bxfigref{cmdlineparams}:
+\item Once you have browsed to the \app{} installation directory and entered \bxshell{testexec.exe}, you can enter the parameters for the test execution.
+\item The test executor has various parameters \bxfigref{cmdlineparams}:
\bxtipp{A list of language codes is available in the reference manual (\bxextref{\gdrefman}{ref,langcodes}).}
\label{cmdlineparams}
@@ -52,15 +52,15 @@
\hline
Database scheme
& \bxshell{-dbscheme <scheme>}\\
- &e.g. \emph{-dbscheme ''Embedded''}\\
+ &e.g. \emph{-dbscheme ''embedded''}\\
\hline
Database username
& \bxshell{-dbuser <username>}\\
- &e.g. \emph{-dbuser ''joebloggs''}\\
+ &e.g. \emph{-dbuser ''username''}\\
\hline
Database password
& \bxshell{-dbpw <password>}\\
- &e.g. \emph{-dbpw ''mypassword''}\\
+ &e.g. \emph{-dbpw ''password''}\\
\hline
Server
& \bxshell{-server <AUT Agent hostname>}\\
@@ -81,15 +81,19 @@
Test Job
& \bxshell{-testjob <testjob name>}\\
&e.g. \emph{-testjob ''job1''}\\
+ \hline
+ Workspace
+ & \bxshell{-data <path to workspace>}\\
+ &e.g. \emph{-data ''C:/Users/Test''}\\
\hline
Data directory
& \bxshell{-datadir <path to external} \\
& \bxshell{test data directory>}\\
- &e.g. \emph{-datadir ''C:/Program Files/guidancer/data''}\\
+ &e.g. \emph{-datadir ''C:/Program Files/Test/Data''}\\
\hline
Result directory
& \bxshell{-resultdir <path to directory>}\\
- &e.g. \emph{-resultdir ''C:/Program Files/guidancer/results''}\\
+ &e.g. \emph{-resultdir ''C:/Program Files/Test/results''}\\
\hline
No run option (optional)
& \bxshell{-n}\\
@@ -120,126 +124,17 @@
&Flags the test results as not relevant \\
& in the test result summary \bxpref{testresprefs}.\\
\hline
-%\caption{Parameters for Command Line Client}
\end{supertabular}
-%% \centering
-%% \label{cmdlineparams}
-%% \begin{longtable}{|l|l|}
-%% %\begin{table}[h]
-
-%% %\begin{tabular}{|l|l|}
-%% \hline
-%% \textbf{Detail}&\textbf{Parameter}\\
-%% \hline
-%% Help
-%% &\bxshell{-h}\\
-%% & Gives parameter help\\
-%% \hline
-%% Project name
-%% & \bxshell{-project <project name>}\\
-%% &e.g. \emph{-project ''ExampleProject''}\\
-%% \hline
-%% Project version
-%% & \bxshell{-version <project version>}\\
-%% &e.g. \emph{-version ''1.3''}\\
-%% \hline
-%% \gdaut{} configuration name
-%% & \bxshell{-autconfig <configuration name>}\\
-%% &e.g. \emph{-autconfig ''localconfiguration''}\\
-%% \hline
-%% \gdaut{} ID
-%% & \bxshell{-autid <ID>}\\
-%% &e.g. \emph{-autid ''SimpleAdder1''}\\
-%% \hline
-%% Configuration file
-%% & \bxshell{-c <path to configuration file>}\\
-%% &e.g. \emph{-c ''C:/Program Files/guidancer/config''}\\
-%% \hline
-%% Database scheme
-%% & \bxshell{-dbscheme <scheme>}\\
-%% &e.g. \emph{-dbscheme ''Embedded''}\\
-%% \hline
-%% Database username
-%% & \bxshell{-dbuser <username>}\\
-%% &e.g. \emph{-dbuser ''joebloggs''}\\
-%% \hline
-%% Database password
-%% & \bxshell{-dbpw <password>}\\
-%% &e.g. \emph{-dbpw ''mypassword''}\\
-%% \hline
-%% Server
-%% & \bxshell{-server <AUT Agent hostname>}\\
-%% &e.g. \emph{-server ''localhost''}\\
-%% \hline
-%% Port number
-%% & \bxshell{-port <port number>}\\
-%% &e.g. \emph{-port ''60000''}\\
-%% \hline
-%% Language
-%% & \bxshell{-language <language code>}\\
-%% &e.g. \emph{-language ''en\_US''}\\
-%% \hline
-%% Test Suite
-%% & \bxshell{-testsuite <testsuite name>}\\
-%% &e.g. \emph{-testsuite ''suite1''}\\
-%% \hline
-%% Test Job
-%% & \bxshell{-testjob <testjob name>}\\
-%% &e.g. \emph{-testjob ''job1''}\\
-%% \hline
-%% Data directory
-%% & \bxshell{-datadir <path to external test data directory>}\\
-%% &e.g. \emph{-datadir ''C:/Program Files/guidancer/data''}\\
-%% \hline
-%% Result directory
-%% & \bxshell{-resultdir <path to directory>}\\
-%% &e.g. \emph{-resultdir ''C:/Program Files/guidancer/results''}\\
-%% \hline
-%% No run option (optional)
-%% & \bxshell{-n}\\
-%% &e.g. \emph{-n}\\
-%% &Checks if the \gdsuite{} is startable.\\
-%% \hline
-%% Quiet option (optional)
-%% & \bxshell{-q} \\
-%% &e.g. \emph{-q}\\
-%% &Does not give out test information.\\
-%% \hline
-%% Database URL (optional)
-%% & \bxshell{-dburl <URL>}\\
-%% &e.g. \emph{-dburl ''db.example.de''}\\
-%% &If no URL is given, the default will be used.\\
-%% \hline
-%% Timeout (optional)
-%% & \bxshell{-timeout <timeout in seconds>}\\
-%% &e.g. \emph{-timeout ''3600''}\\
-%% &Enter an optional timeout for the command line client.\\
-%% \hline
-%% No screenshot (optional)
-%% & \bxshell{-s }\\
-%% \hline
-%% Test results not relevant (optional)
-%% & \bxshell{-r }\\
-%% &\\
-%% &Flags the test results as not relevant in the test result summary \bxpref{testresprefs}.\\
-%% \hline
-%% \caption{Parameters for Command Line Client}
-%% \end{longtable}
-
-
-\item You can either enter a \gdsuite{} to be executed or a \gdjob{}. Only one of these two commands is accepted for the command line client.
-\item If the \gdaut{} you want to test was started with the \bxname{gdrun} command, you must enter an \gdaut{} ID. If your \gdaut{} will be started with an \gdaut{} configuration, then enter the configuration name.
-%For example, two \gdsuites{} called \bxname{Test,Part1} and \bxname{Test,Part2} would have to be entered as:\\
-%\bxshell{-testsuites ''Test$\backslash$Part1,Test$\backslash$Part2''}
-%\item If you have used quotes in your \gdsuite{} name, and these are a special symbol for your operating system, then the quotes must be masked with backslashes.
+\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.
+\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 \app{} Command Line Client 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 Command Line Client. When entering the standard parameters for the Command Line Client, 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. \\
+\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 \gdprojects{}, 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 \gdsuites{} you specified, in the order you wrote them.
+\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 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.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/starting.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/starting.tex
index f8a22d762..176733cba 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/starting.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/starting.tex
@@ -15,12 +15,12 @@
%% % ----------------------------------------------------------------------
%% \end{document}
-\index{Command Line Client}
+\index{Test Executor}
\begin{enumerate}
\item In a command line interface, locate the \app{} installation directory and open the \app{} directory within it.
-\item Enter \bxshell{GUIdancerCMD.exe}.
+\item Enter \bxshell{testexec.exe}.
-This will run the executable \emph{GUIdancerCMD.exe}.
+This will run the executable \emph{testexec.exe}.
\item Do not press \bxkey{enter} until you have entered the necessary parameters. See the next section for details on the parameters.
\end{enumerate}
\bxtipp{Be sure to start the \gdagent{} before executing a test}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/CONTENT.tex
index 0a7f533df..cce9c1df9 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/CONTENT.tex
@@ -41,7 +41,7 @@
\subsection{Renaming component names}
\gdhelpid{guidancerComponentNameBrowserContextId}{Component Name Browser}
-\gdhelpid{objectMapEditorContextId}{Object Mapping}
+%\gdhelpid{objectMapEditorContextId}{Object Mapping}
\gdhelpid{renameComponentNameContextId}{Rename Component Name Dialog}
\label{TasksRenameCompName}
\input{Tasks/Compnames/rename}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/hierarchy.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/hierarchy.tex
index a4187643a..9bc659de2 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/hierarchy.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/hierarchy.tex
@@ -16,7 +16,7 @@ What happens if you want to specify a test that clicks in a table and then selec
The click action is on the \bxname{Graphics Component} and the select cell action is on the \bxname{Table} component -- but you don't want to have two different component names.
-This isn't a problem for \app{}. You can use the same component name for different components as long as these are compatible. So, in this case, the \bxname{Graphics Component} and the \bxname{Table} component can both use the component name \bxname{TableView\_MainTable\_tbl}.
+This isn't a problem for \app{}. You can use the same component name for different components as long as these are compatible. So, in this case, the \bxname{Graphics Component} and the \bxname{Table} component can both use the component name e.g. \bxname{TableView\_MainTable\_tbl}.
\bxwarn{You cannot use the same component name for incompatible types, for example, trees and tables.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/intro.tex
index b23d1ce30..de7c8bf28 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/intro.tex
@@ -1,4 +1,4 @@
-Component names \bxpref{} are the names you use to refer to the user interface components you want your actions to be executed on. These component names are collected and assigned to real components when you carry out object mapping \bxpref{objectmappingtasks}.
+Component names are the names you use to refer to the user interface components you want your actions to be executed on. These component names are collected and assigned to real components when you carry out object mapping \bxpref{objectmappingtasks}.
\bxtipp{A component is an element of the user interface you can execute an action on, e.g. a button, a text field.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/merge.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/merge.tex
index 89497b680..4e19bfe22 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/merge.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/merge.tex
@@ -1,7 +1,8 @@
\index{Component!Names!Merge}
\index{Merge Component Names}
-You can merge two or more component names to one unifying name in the \gdomeditor{} (tree view) and in the \gdcompnamebrowser{}. This makes sense if you have accidentally created two component names for the same component.
+You can merge two or more component names to one unifying name in the %\gdomeditor{} (tree view) and in the
+\gdcompnamebrowser{}. This makes sense if you have accidentally created two component names for the same component.
\bxtipp{The component types must be the same to be able to merge the component names, and the component names must not have already been mapped to different technical names from the \gdaut{}. The component names must all come from the current \gdproject{}, not from any of the reused \gdprojects{}.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/new.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/new.tex
index 9f38abb45..9b4e8b685 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/new.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/new.tex
@@ -13,4 +13,4 @@ A dialog will appear to allow you to enter a component name. We recommend having
The component name you enter will be created and will appear in the \bxname{unassigned component names} category in the \gdomeditor{} and in the \bxname{unused component names} category in the \gdcompnamebrowser{}.
-\bxtipp{Newly created component names have the type \bxname{graphics component} until they are made more concrete, either by mapping them to a technical name or by entering this new name in the \gdcompnamesview{} for a more concrete component type. }
+\bxtipp{Newly created component names have the type \bxname{graphics component} until they are made more specific, either by mapping them to a technical name or by entering this new name in the \gdcompnamesview{} for a more concrete component type. }
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/reassigning.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/reassigning.tex
index 6bb4ae181..4d8e54ce1 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/reassigning.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/reassigning.tex
@@ -12,7 +12,7 @@
\bxtipp{The following section deals with entering component names in the \gdcompnamesview{} when you have added \gdcases{} from the library. For information on component names in \gdsteps{}, see the \gdsteps{} section \bxpref{specsteps}.}
\begin{enumerate}
-\item Once you have added a \gdcase{} from the library of \gdcases{}, you will need to enter a component name for the component you want to test.
+\item Once you have added a \gdcase{} from the library of \gdcases{} \bxpref{usingtemplate}, you will need to enter a component name for the component you want to test.
\item In the \gdcompnamesview{}, you will see the \bxname{old name} for this component, which was given in the \gdstep{} contained in the library \gdcase{}. The old name is just a placeholder and should be \bxname{reassigned} (\bxfigref{compnamesview}).
\begin{figure}[h]
@@ -24,7 +24,7 @@
\end{figure}
-\bxtipp{Reassigning component names: by entering a different component name in the \gdcompnamesview{} you create a new reference to a component in the \gdaut{}. You can create as many new component names as you like for each \gdcase{}. This lets you execute the same actions on different (but compatible) components without having to specify whole new \gdcases{} to do this. Reassigning is different to \bxname{renaming} - whereby you simply change the name of a reference to a component \bxpref{TasksRenameCompName}. }
+\bxtipp{When you enter a component name in the \gdcompnamesview{}, you create a new reference to a component in the \gdaut{}. This component name appears in the \gdomeditor{} to be mapped to a component in your \gdaut{}. A \gdcase{} containing component names to be reassigned can therefore be used at a variety of different places to test different actual components. If you want to rename a component name, you can do so in the \gdcompnamebrowser{} \bxpref{TasksRenameCompName}.}
\item In the \bxname{new name} field, enter your name for this component, e.g. \bxshell{MainWindow\_NavigationTree\_tre}.
@@ -52,7 +52,7 @@ We recommend using naming conventions for component names \bxpref{BPComponentNam
\label{TasksCompNamesCheckbox}
Select the checkbox on the left of the \gdcompnamesview{} to be able to see and edit (reassign) this component name when you reuse the parent of the \gdcase{} you are editing.
-This is useful for creating flexible keywords that can click either the cancel button or the ok button in a dialog, for example. Depending on what you want the keyword to do when you reuse it, you can overwrite the name to \bxname{LoginDialog\_OK\_btn} or \bxname{LoginDialog\_Cancel\_btn}.
+This is useful for creating flexible keywords that can be used for the same workflow on different components. Depending on what you want the keyword to do when you reuse it, you can reassign the name to test different components in the \gdaut{}.
\subsubsection{Changing component names}
If you newly reassign component names in your test hierarchy that were themselves later reassigned, you will be shown a message in the \gdcompnamesview{}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/rename.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/rename.tex
index 98de159a7..a85bd0bfa 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/rename.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Compnames/rename.tex
@@ -1,7 +1,7 @@
\index{Component!Names!Rename}
\index{Rename!Component Name}
-Use the rename function to change the name of a component name in your test specification. Whereas \bxname{reassigning} component names results in a new component name being created \bxpref{TasksReassignCompName}, renaming just changes the name.
+Use the rename function to change the name of a component name in your test specification. Whereas \bxname{reassigning} component names results in a new component name being created \bxpref{TasksReassignCompName}, renaming just changes the name at all places where it is used.
You can rename component names in the \gdcompnamebrowser{} and in the \gdomeditor{}.
\begin{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Editors/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Editors/CONTENT.tex
index 335c88a07..fb2a378ff 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Editors/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Editors/CONTENT.tex
@@ -44,7 +44,7 @@
\label{TasksEditorDeactivate}
\input{Tasks/Editors/deactivate}
-\subsection{Extracting \gdcases{} from editors}
+\subsection{Extracting \gdcases{} from editors: Refactoring}
\gdhelpid{guidancerSpecTestCaseEditorContextId}{Test Case Editor}
\gdhelpid{testSuiteEditorContextId}{Test Suite Editor}
\label{TasksEditorExtract}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/CONTENT.tex
index 59b206eff..9f097430d 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/CONTENT.tex
@@ -5,7 +5,7 @@
\index{Verify failed}
\index{Configuration error}
-\gdehandlers{} are \gdcases{} used to deal with expected errors during test execution. When an error occurs, the current \gdcase{} is searched for an \gdehandler{} for that error type. If none is found, the parent \gdcase{} is searched, and so on. If no \gdehandler{} for the test is found, then a default \gdehandler{} is activated. Default \gdehandlers{} are specified in the \gdsuite{} properties \bxpref{confsuite}.
+\gdehandlers{} are \gdcases{} used to deal with deviations during test execution. When an error occurs, the current \gdcase{} is searched for an \gdehandler{} for that error type. If none is found, the parent \gdcase{} is searched, and so on. If no \gdehandler{} for the test is found, then a default \gdehandler{} is activated. Default \gdehandlers{} are specified in the \gdsuite{} properties \bxpref{confsuite}.
The advantage of adding your own \gdehandlers{} is that you can define specific behavior for certain errors in each \gdcase{}. An \gdehandler{} can be an empty \gdcase{}, or can contain \gdcases{} to be executed when the error occurs.
@@ -16,6 +16,7 @@ For each \gdehandler{}, you must specify:
\end{description}
\subsection{Adding \gdehandlers{} to a \gdcase{}}
+\gdhelpid{guidancerSpecTestCaseEditorContextId}{Test Case Editor}
\input{Tasks/Eventhandlers/add}
\subsection{Event types}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/add.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/add.tex
index 5ef7fa680..945efd691 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/add.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Eventhandlers/add.tex
@@ -10,7 +10,7 @@ This section deals with adding \gdehandlers{} to \gdcases{}. For information on
\item Select\\
\bxmenu{Add}{\gdcase{} as \gdehandler{}}{} \\from the context-sensitive menu in the editor or use \bxkey{Ctrl+Enter}.
-\bxtipp{You can also drag the \gdcase{} you want to use straight into the \gdehandlers{} area of the \gdcase{}. }
+\bxtipp{You can also drag the \gdcase{} you want to use straight into the \gdehandlers{} area of at the bottom of th the \gdtestcaseeditor{}. }
\item Choose a \gdcase{} to add from the dialog that appears.
\bxtipp{You can't add a \gdcase{} to itself as an \gdehandler{}, because this would create an infinite loop. }
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/CONTENT.tex
index 92c33bb5d..60935c7fd 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/CONTENT.tex
@@ -6,6 +6,7 @@
\subsection{Testing different \gdauts{} in one test run}
\gdhelpid{testExecViewContextId}{Test Suite Browser}
\gdhelpid{runningAutsViewContextId}{Running AUTs View}
+\gdhelpid{guidancerTestJobEditorContextId}{Test Job Editor}
\label{TasksSwitchAUT}
\input{Tasks/Jobs/changeaut}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/changeaut.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/changeaut.tex
index 1c3d08fed..1c7e381c2 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/changeaut.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/changeaut.tex
@@ -5,7 +5,6 @@ The \gdauts{} can be the same actual \gdaut{} which has been started multiple ti
You can test \gdauts{} that were started independently, or \gdauts{} that are launched by other \gdauts{}.
-
\subsubsection{Testing independently started \gdauts{}}
\index{Test Job}
@@ -15,7 +14,7 @@ To be able to test multiple \gdauts{} that are \bxname{not} started by each othe
\item The \gdauts{} are either written with the same toolkit (e.g. Swing) or,
\item you have specified your \gdproject{} at the \bxname{concrete} level, and will only be testing areas of the \gdauts{} that can be tested with the actions that are valid for all \gdaut{} types (i.e. no RCP-specific components are involved in the test) \bxpref{projtoolkit}.
\item The \gdauts{} are all defined in the same \gdproject{}.
-\item The first \gdaut{} can either be started using the \bxname{autrun} command \bxpref{gdrun} or via an \gdaut{} configuration \bxpref{configuringaut}. Any other \gdauts{} required for the \gdjob{} must have been started with the \bxname{autrun} command.
+\item The first \gdaut{} can either be started using the \bxname{autrun} command \bxpref{autrun} or via an \gdaut{} configuration \bxpref{configuringaut}. Any other \gdauts{} required for the \gdjob{} must have been started with the \bxname{autrun} command.
\end{itemize}
\bxtipp{To run \gdjobs{} from the test executor, all \gdauts{} for the test run must be started with the \bxname{autrun} command.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/intro.tex
index 0fc93cb7d..ab7f18b4c 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Jobs/intro.tex
@@ -2,7 +2,7 @@
You can create a \gdjob{} when you want to execute a collection of \gdsuites{} after each other.
-The \gdsuites{} can test the same \gdaut{}, different instances of the same \gdaut{}, or different \gdauts{} entirely.
+The \gdsuites{} can test different instances of the same \gdaut{}, or different \gdauts{} entirely.
You do not have to create a \gdjob{} if you only want to run tests on one instance of one \gdaut{}. To do this, you can use a \gdsuite{} \bxpref{WorkingWithSuites}. A \gdjob{} is most useful when you want to switch between two \gdauts{} (either the same \gdaut{} or a different one) in one test run.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Manual/create.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Manual/create.tex
index f57ebd1b4..9d5e90b4b 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Manual/create.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Manual/create.tex
@@ -1,4 +1,4 @@
-\app{} also lets you create manual tests to be executed and analyzed in the \app{} software.
+\app{} also lets you create manual tests to be executed and analyzed.
A \gdcase{} containing manual \gdsteps{} is the same as an automated \gdcase{} for all intents and purposes. You can add data, reuse it in other \gdcases{}, and add it to \gdsuites{} to be executed. The only difference is during execution: manual tests are executed in an interactive mode \bxpref{TasksManualExec}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/CONTENT.tex
deleted file mode 100644
index 40601101d..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/CONTENT.tex
+++ /dev/null
@@ -1,49 +0,0 @@
-\subsection{Working with models in \app{}}
-\protect\gdhelpid{org.eclipse.ui.resource_view_context}{Navigator View}
-\input{Tasks/Modelling/models}
-
-\subsection{Creating a \gdproject{} for modeling}
-\protect\gdhelpid{org.eclipse.ui.resource_view_context}{Navigator View}
-\label{TasksMBTCreateProject}
-\input{Tasks/Modelling/createproject}
-
-\subsection{Creating a new model diagram}
-\protect\gdhelpid{org.eclipse.ui.resource_view_context}{Navigator View}
-\gdhelpid{newModelWizardContextId}{New Model Wizard}
-\label{TasksMBTCreateModel}
-\input{Tasks/Modelling/createmodel}
-
-\subsection{Importing models from UML}
-\protect\gdhelpid{org.eclipse.ui.resource_view_context}{Navigator View}
-\gdhelpid{importModelWizardContextId}{Import Model Wizard}
-\label{TasksMBTImport}
-\input{Tasks/Modelling/import}
-
-
-\subsection{Creating models: adding \gdcases{}, categories, parameters and referenced \gdcases{}}
-\gdhelpid{guidancerModelEditorContextId}{Modeling Editor}
-\label{TasksMBTModel}
-\input{Tasks/Modelling/add}
-
-
-\subsection{Altering the appearance of models}
-\gdhelpid{guidancerModelEditorContextId}{Modeling Editor}
-\input{Tasks/Modelling/appearance}
-
-
-\subsection{Options for working with models: zoom, print, undo etc.}
-\gdhelpid{guidancerModelEditorContextId}{Modeling Editor}
-\input{Tasks/Modelling/options}
-
-\subsection{Generating \gdcases{} and categories from models}
-\gdhelpid{generationWizardContextId}{Generating Models}
-\gdhelpid{guidancerModelEditorContextId}{Modeling Editor}
-\label{TasksMBTGenerate}
-\input{Tasks/Modelling/generate}
-
-\subsection{Validating models}
-\gdhelpid{guidancerModelEditorContextId}{Modeling Editor}
-\label{TasksMBTValidate}
-\input{Tasks/Modelling/validate}
-
-%in UI stuff - the modeling perspective
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/GenerateDialog.png b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/GenerateDialog.png
deleted file mode 100644
index 3ebc13b86..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/GenerateDialog.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/ModelError.png b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/ModelError.png
deleted file mode 100644
index eb769acbd..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/ModelError.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/Model_ReusedTCs.png b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/Model_ReusedTCs.png
deleted file mode 100644
index a5ac76bda..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/PS/Model_ReusedTCs.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/add.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/add.tex
deleted file mode 100644
index eb35ea583..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/add.tex
+++ /dev/null
@@ -1,61 +0,0 @@
-\index{Modeling!Add Elements}
-\index{Add Elements to Model}
-
-Once you have created a modeling \gdproject{} \bxpref{TasksMBTCreateProject} and created a model \bxpref{TasksMBTCreateModel} or imported one \bxpref{TasksMBTImport}, you can start working on your model.
-
-\bxtipp{We recommend validating your model frequently \bxpref{TasksMBTValidate}.}
-\begin{enumerate}
-\item If the \gdmodeleditor{} is not open, open it by double-clicking on the model you want to work on in the \gdnavview{}.
-\item In the palette on the right-hand side of the \gdmodeleditor{}, you will see the four \bxname{nodes} and the one \bxname{connector} that you can use to create your models. These are:
-\begin{description}
-\item [\gdcase{}:]{These are the building blocks of your test. When you generate your model, they become normal \app{} \gdcases{} \bxpref{WorkingWithTestCases}. Use \gdcases{} to model actions or sequences of actions in your \gdaut{}. }
-\item [\gdcase{} reference:]{As with any \app{} test, \gdcases{} can be reused in other \gdcases{}. Add \gdcase{} references to the \bxname{reused \gdcase{}} area in a \gdcase{} node to indicate that you want to reference a \gdcase{} here. You will need to add a connector line between the \gdcase{} reference and the referencing \gdcase{} in your model.}
-\item [Parameter:]{\gdcases{} can have parameters for data that this \gdcase{} will reference. You can add parameters to the \bxname{parameter} area in \gdcase{} nodes. Adding parameters in this way is the equivalent of referencing parameters in the specification perspective using the equals sign \bxpref{TasksTestdataReferences}.}
-\item [Category:]{You can group the \gdcases{} in your model into categories. These will later be generated into \app{} categories in the \gdtestcasebrowser{} \bxpref{TasksTCCats}. Use categories to organize your \gdcases{}.}
-\item [Define reused \gdcase{}:]{Once you have added a \gdcase{} reference to a \gdcase{} in your model, you must use this connector to show which \gdcase{} the reference reuses. Click and drag the connector from the \gdcase{} reference to the \gdcase{} it reuses.}
-\end{description}
-\end{enumerate}
-
-\subsubsection{Adding \gdcases{} to the model}
-To add a \gdcase{} to the model:
-\begin{enumerate}
-\item Click once on the \gdcase{} node in the palette then click in the \gdmodeleditor{} to place the \gdcase{}. The \gdcase{} appears on the canvas.
-\bxtipp{You do not need to drag and drop the elements from the palette.}
-\item Enter a name for the \gdcase{} either directly in the model, or in the \gdpropview{} in the modeling perspective.
-\end{enumerate}
-
-\subsubsection{Adding parameters to \gdcases{} in the model}
-To add parameters to a \gdcase{} in the model:
-\begin{enumerate}
-\item Click once on the \bxname{Parameter} node in the palette.
-\item Click in the \bxname{parameter} area of the \gdcase{} you want to add the parameter to in the \gdmodeleditor{}. The parameter appears in the \gdcase{}.
-\item Name the parameter either directly in the model, or in the \gdpropview{} in the modeling perspective.
-\item In the \gdpropview{}, select the type of parameter: \bxname{String, Integer, Boolean} or \bxname{Variable}.
-\end{enumerate}
-
-\subsubsection{Adding referenced \gdcases{} and connections in the model}
-To reference a \gdcase{} in the model:
-\begin{enumerate}
-\item Click once on the \bxname{\gdcase{} Reference} node in the palette.
-\item Click once in the \bxname{reused \gdcase{}} area of the \gdcase{} you want to add the \gdcase{} reference to in the model. The \gdcase{} reference appears in the \gdcase{}.
-\item Click once on the \bxname{Define Reused \gdcase{}} node in the palette.
-\item In the canvas, drag the connection from the reused \gdcase{} you just added to the actual \gdcase{} you want to reference. The name of the \gdcase{} you are referencing will automatically appear in the referenced \gdcase{} (\bxfigref{ModelReusedTCs}).
-\end{enumerate}
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics{Tasks/Modelling/PS/Model_ReusedTCs}
-\caption{Model showing referenced Test Cases}
-\label{ModelReusedTCs}
-\end{center}
-\end{figure}
-
-\subsubsection{Adding categories to the model}
-To add a category to the model:
-\begin{enumerate}
-\item Click once on the \bxname{Category} node in the palette and then click in the \gdmodeleditor{} to place the category. The category appears on the canvas.
-\item Enter a name for the category, either directly in the model or in the \gdpropview{} in the modeling perspective.
-\item To add items already on the canvas to a category, drag the item and drop it into the category area.
-\item To add items directly to a category, select the item from the palette and click into the category to place it here.
-\bxtipp{When the category is selected, you can see a small arrow in the left-hand corner. This arrow must be pointing down to be able to add items to the category.}
-\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/appearance.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/appearance.tex
deleted file mode 100644
index 5dc08f095..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/appearance.tex
+++ /dev/null
@@ -1,8 +0,0 @@
-\index{Modeling!Appearance}
-\index{Appearance!Model}
-
-There are various ways of altering the appearance of the model and the canvas.
-
-In the main menu, under the \bxname{Modeling} menu, you can alter details about the fonts, colors and lines as well as choosing whether to show grids and rulers. These options are also available in the \gdpropview{} in the modeling perspective under the \bxname{Appearance} and \bxname{Rulers \& Grid} tabs.
-
-You can also set appearance features in the preferences for modeling \bxpref{TasksPrefsModel}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createmodel.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createmodel.tex
deleted file mode 100644
index 37a14c07d..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createmodel.tex
+++ /dev/null
@@ -1,16 +0,0 @@
-\index{Modeling!Create Model Diagram}
-\index{Model Diagram!Create}
-
-
-To be able to create a model, you must first have created a \gdproject{} in the \gdnavview{} \bxpref{TasksMBTCreateProject}.
-
-\begin{enumerate}
-\item In the \gdnavview{}, click the \bxcaption{Create New \gdcase{} Model} button select:\\
-\bxmenu{New}{Other}{}\\
-from the context-sensitive menu.
-\item In the wizard that appears, select \bxname{Test Case Model} from the \bxname{Models} category.
-\item Click \bxcaption{Next}.
-\item Select or enter the \gdproject{} you want to create the diagram in.
-\item Name the new model.
-\item Click \bxcaption{Finish}. The model diagram you created will appear in the \gdnavview{} in the \gdproject{} you specified. The \gdmodeleditor{} will open. \item Now you have created a model diagram, you can add elements to it to model your test \bxpref{TasksMBTModel}.
-\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createproject.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createproject.tex
deleted file mode 100644
index 92a20a5c3..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/createproject.tex
+++ /dev/null
@@ -1,18 +0,0 @@
-\index{Project!Create for Model}
-\index{Create Model Project}
-
-The first thing to do when you want to work with models in \app{} is to create an Eclipse Project in which the models will be managed and saved. The \gdproject{} will be saved in your workspace.
-
-\begin{enumerate}
-\item Switch to the modeling perspective if you have not already done so. You can do this by selecting:\\
-\bxmenu{Window}{Open Perspective}{Modeling Perspective}
-\item In the \gdnavview{}, click the \bxcaption{Create New Project} button
-or select:\\
-\bxmenu{New}{Project}{}\\
-from the context-sensitive menu.
-\item In the wizard that appears, select \bxname{Project} from the \bxname{General} category.
-\item Click \bxcaption{Next}
-\item Enter a \gdproject{} name. You can decide whether to keep the \gdproject{} in your workspace or link to it from your workspace.
-\item Click \bxcaption{Finish}. The \gdproject{} you just created will appear in the \gdnavview{}. It contains the file \bxname{.project}. Do not delete this file!
-\item Now you have created a \gdproject{}, you can create a new model diagram \bxpref{TasksMBTCreateModel} or import models \bxpref{TasksMBTImport}.
-\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/generate.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/generate.tex
deleted file mode 100644
index 2ecb6ec85..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/generate.tex
+++ /dev/null
@@ -1,43 +0,0 @@
-\index{Generate Model}
-\index{Modeling!Generate}
-
-In order to be able to generate \gdcases{} and categories from a model, you must have:
-\begin{itemize}
-\item Created a modeling \gdproject{} \bxpref{TasksMBTCreateProject}.
-\item Created \bxpref{TasksMBTCreateModel} or imported \bxpref{TasksMBTImport} a model diagram.
-\item Created \bxpref{newproject} or opened \bxpref{loadproject} a \app{} \gdproject{}.
-\end{itemize}
-
-\begin{enumerate}
-\item When you are ready to generate, select:\\
-\bxmenu{Modeling}{Generate}{}\\ from the menu or select the \bxcaption{Generate} button on the toolbar \gdmarpar{../../../share/PS/transform}{Generate}.
-\item In the dialog that appears (\bxfigref{GenerateDialog}), you can configure what you want to generate.
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics{Tasks/Modelling/PS/GenerateDialog}
-\caption{Generation Dialog}
-\label{GenerateDialog}
-\end{center}
-\end{figure}
-
-
-\begin{description}
-\item [Validating]{ the model is the prerequisite for all other options. It ensures that the model can be successfully generated.}
-\item [Model \gdcases{} to \app{} \gdcases{}:]{This converts any \gdcases{} you have created in the model to corresponding \app{} \gdcases{} in the \gdtestcasebrowser{}. Generated \gdcases{} have a green corner. }
-\item [Model categories to \app{} categories:]{This converts categories you have created in the model to categories in the \gdtestcasebrowser{}. Generated categories are slightly green. }
-\item [Sort generated artefacts:]{This option organizes your \gdcases{} into categories as specified in the model. If you turn this option off, your \gdcases{} will not be created in the modeled categories, nor will any \gdcases{} from previous generations be moved back into the modeled categories in the \gdtestcasebrowser{} (if you re-organized \gdcases{} for example).}
-\end{description}
-\item Click \bxcaption{Finish} to start the generation. During the generation, the status of the various actions is shown in the console. Once the generation is complete, you will be able to see the items you generated in the \gdtestcasebrowser{}.
-\bxtipp{Parameters that are part of generated \gdcases{} are \bxname{locked} by default, and cannot be changed or deleted. You can see the parameters and unlock them in the \gdtestcaseeditor{} using the \bxname{edit parameters} dialog \bxpref{editparams}. }
-\item Once the \gdcases{} have been generated, you can fill them with the necessary \gdcases{} from the library in \app{} to create your tests.
-%regeneration, model always right
-\end{enumerate}
-
-\subsubsection{Regenerating models}
-After generating a model for the first time, you may want to make changes and regenerate it. This is not a problem in \app{} -- it will not result in duplicates of previously created items being made. Any changes made to the model (if you have added or renamed items, for example) will be reflected in the \gdcase{} generation. However, there are two points to bear in mind:
-
-\begin{description}
-\item [Deleting objects from the model:]{Any objects you delete from the model will not be deleted from the \gdcase{} browser. }
-\item [The model takes precedence over other changes:]{If you have made changes to the generated \gdcases{} in the \gdtestcasebrowser{} or \gdtestcaseeditor{} (e.g. renamed them, added other \gdcases{}), these changes will be lost when you regenerate the model. }
-\end{description}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/import.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/import.tex
deleted file mode 100644
index 559cd9d98..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/import.tex
+++ /dev/null
@@ -1,27 +0,0 @@
-\index{Model Diagram!Import}
-\index{Import!Model Diagram}
-You can import models directly into \app{} which have been created with the Eclipse UML2 Tools. The UML2 tools project is a sub-project of the Model Development Tools project.
-
-In this project, models are always saved in two files - \bxname{*.umlusc} and \bxname{*.uml}. The \app{} import dialog does not show the *.uml files, but it is important that these *.uml files are in the same folder as the *.umlusc files.
-
-
-
-\begin{enumerate}
-\item In the \gdnavview{}, select:\\
-\bxmenu{Import}{}{}\\
-from the context-sensitive menu.
-\item In the wizard that appears, select \bxname{Import external Model File} from the \bxname{Model} category.
-\item Click \bxcaption{Next}.
-\item Enter of browse to the model diagram you want to import (the *.umlusc file).
-\item Select or enter the \gdproject{} you want to import the diagram into.
-\item Click \bxcaption{Finish}. The model diagram you specified will be imported into your workspace as a \app{} model digram. It appears in the \gdnavview{} in the \gdproject{} you specified.
-\item The following elements are imported from the diagram:
-\begin{itemize}
-\item Use cases
-\item Relations between use cases (\bxname{include} relationships)
-\item Packages
-\end{itemize}
-
-Now you have imported a model, you can make changes to it \bxpref{TasksMBTModel}, validate it \bxpref{TasksMBTValidate} or generate it \bxpref{TasksMBTGenerate}.
-\end{enumerate}
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/models.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/models.tex
deleted file mode 100644
index f76077bee..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/models.tex
+++ /dev/null
@@ -1,10 +0,0 @@
-\index{Modeling}
-
-The \app{} modeling perspective has been designed to help teams get started with automated testing early on in the development process by allowing the import of UML diagrams and the subsequent generation of \gdcase{} structures from the models.
-
-Testing early is important to find errors when they are cheaper to fix, yet it is often difficult to know where to start testing or how to structure the tests to be as reusable and maintanable as possible.
-
-At this stage, it is important to realize that the aim is not to derive complete, functional tests from complex models. Instead, the imported use case diagrams and activity diagrams, and the \gdcases{} generated from them, can be used to see which structures (\gdcases{}) will need to be reused throughout the test, and what sequences of \gdcases{} will need to be created to cover the use cases.
-
-
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/options.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/options.tex
deleted file mode 100644
index 8e210f780..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/options.tex
+++ /dev/null
@@ -1,15 +0,0 @@
-\index{Modeling!Options}
-
-
-The modeling perspective offers different ways of grouping and visualising your model, as well as useful actions to help you work with the model:
-
-\begin{description}
-\item [Zooming:]{You can use the context-sensitive menu and the main menu to zoom into and out of the canvas. }
-\item [Printing:]{In the context-sensitive menu for the canvas, you can opt to print the model. In the main menu you can choose to see page breaks in the \gdmodeleditor{}. }
-\item [Saving as an image:]{You can save the model as an image file using the context-sensitive menu in the \gdmodeleditor{}. }
-\item [Undo, Redo, Cut, Copy and Paste]{ actions are all available in the context-sensitive menu in the \gdmodeleditor{}. }
-\item [Arranging:]{You can either arrange the selected items in the \gdmodeleditor{} or arrange all of the items automatically.}
-\item [Adding notes:]{You can add notes to the model and to the elements within it. Notes are, however, not generated with the \gdcases{} from the model.}
-\end{description}
-
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/validate.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/validate.tex
deleted file mode 100644
index cfeea538e..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Modelling/validate.tex
+++ /dev/null
@@ -1,20 +0,0 @@
-\index{Validate Model}
-\index{Modeling!Validate}
-
-You can validate your model at any time by selecting:\\
-\bxmenu{Modeling}{Validate}{}. \\
-
-
-Or by clicking the \bxcaption{validate} button on the toolbar.
-The validation ensures that the model is fit to be generated, and does not contain any errors.
-\gdmarpar{../../../share/PS/validate}{Validate}
-
-If there are errors in the model, you will see this in the console output. In the \gdmodeleditor{} itself, the places with errors will be marked with a red cross. Hovering over the cross will show a tooltip with information on the error (\bxfigref{ModelError}).
-
-\begin{figure}
-\begin{center}
-\includegraphics{Tasks/Modelling/PS/ModelError}
-\caption{Model showing an error}
-\label{ModelError}
-\end{center}
-\end{figure}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/editor.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/editor.tex
index 89c357520..ca9f39b44 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/editor.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/editor.tex
@@ -22,7 +22,7 @@
\gdhelpid{objectMapEditorContextId}{Object Mapping}
\input{Tasks/Objectmapping/refresh}
-\subsubsection{Finding components in the \gdaut{} via the \gdomeditor{}}
+\subsubsection{Finding components in the \gdaut{} via the \gdomeditor{}: highlight in \gdaut{}}
\gdhelpid{objectMapEditorContextId}{Object Mapping}
\input{Tasks/Objectmapping/showwhereused}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/openOME.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/openOME.tex
index e2f9b0f0e..8ea9621d8 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/openOME.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/openOME.tex
@@ -1,7 +1,7 @@
\begin{enumerate}
\item Open the \gdomeditor{} by selecting the \gdsuite{} whose components you want to map and selecting:\\
\bxmenu{Open with}{\app{} \gdomeditor{}}{}.
-\bxtipp{The \gdomeditor{} also opens automatically when you start the \gdomm{}. }
+\bxtipp{The \gdomeditor{} also opens automatically when you start the \gdomm{} via the toolbar. }
The \gdomeditor{} for the \gdaut{} used by this \gdsuite{} will appear (see \bxfigref{objectmappingeditor}).
\bxtipp{You can see the name of the \gdaut{} you are mapping in the tab of the editor}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/robust.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/robust.tex
index 820c06901..0548c55a6 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/robust.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/robust.tex
@@ -27,12 +27,5 @@ If you get a \bxname{component not found} error, or \app{} selects the wrong com
This updates this component for the whole test.
-%\item If you cannot assign the newly mapped component to the old component name because the component types are incompatible, then you will have to change the test specification to use different \gdcase{} from the library.
-
-%This component will then be updated in all of the places you have used this \gdcase{}.
-%\bxtipp{It is easier to remap changed components if you use \bxname{abstract} components in your \gdsteps{} \bxpref{}.}
-
-
-
\clearpage
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/showwhereused.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/showwhereused.tex
index 7af3594b9..e620ecfe0 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/showwhereused.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/showwhereused.tex
@@ -18,7 +18,15 @@
\index{Search!Component in AUT}
\index{Search!Components in Test Cases}
\label{searchcomponentaut}
-In the \gdomeditor{}, as well as the normal search function \bxpref{TasksFindDialog} you can search for a component you have already mapped) in the \gdaut{}
+In the \gdomeditor{}, you can search for:
+
+\begin{itemize}
+\item All the places where a component name has been used in the test \bxpref{TasksShowWhereUsedCompName}
+\item The specific place where a particular component name comes from in the test \bxpref{TasksShowWhereUsedCompName}
+\item The technical component in the \gdaut{} (see below).
+\end{itemize}
+
+\textbf{Highlighting a component in the \gdaut{}}\\
To search for components in the \gdaut{}, the \gdomeditor{} must be open \bxpref{TasksOpenOME}, and the \gdaut{} must be running \bxpref{startaut} in the \gdomm{} \bxpref{TasksOMCollect}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/CONTENT.tex
index c415f693f..2233412c0 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/CONTENT.tex
@@ -8,23 +8,24 @@
% copyright by BREDEX GmbH 2004
% --------------------------------------------------------
-Open the \app{} preferences dialog (\bxfigref{gdprefs}) by selecting:\\
-\bxmenu{Window}{Preferences}{}.
+Open the preferences dialog (\bxfigref{gdprefs}) by selecting:\\
+\bxmenu{Window}{Preferences}{}.
-\subsection{\app{} preferences}
-\gdhelpid{prefPageBasicContextId}{GUIdancer Preferences}
+\subsection{Test preferences}
+\gdhelpid{prefPageBasicContextId}{Test Preferences}
\input{Tasks/Preferences/gdprefs}
-\subsection{Appearance preferences}
-\gdhelpid{appearancePrefPageContextId}{Appearance Preferences}
-\input{Tasks/Preferences/appearance}
-
\subsection{\gdagent preferences}
\gdhelpid{prefPageServerContextId}{AUT Agent Preferences}
\gdhelpid{autConfigPropDialogContextId}{Adding/editing AUT configurations}
\gdhelpid{autConfigSettingWizardPagePageContextId}{Configuring an AUT}
\input{Tasks/Preferences/serverConfigPrefPage}
+\subsection{\gddb{} preferences}
+\gdhelpid{databaseConnectionConfigurationDialogContextId}{Database connection preferences}
+\label{TasksPrefsDB}
+\input{Tasks/Preferences/dbprefs}
+
\subsection{Editor preferences}
\gdhelpid{editorPrefPageContextId}{Editor Preferences}
@@ -32,6 +33,7 @@ Open the \app{} preferences dialog (\bxfigref{gdprefs}) by selecting:\\
\subsection{Object mapping preferences}
\gdhelpid{prefPageObjectMapContextId}{Object Mapping Preferences}
+\gdhelpid{objectMapEditorContextId}{Object Mapping}
\label{TasksPrefsOMM}
\input{Tasks/Preferences/omprefs}
@@ -40,18 +42,9 @@ Open the \app{} preferences dialog (\bxfigref{gdprefs}) by selecting:\\
\label{TasksPrefsObsModeJava}
\input{Tasks/Preferences/obsprefsjava}
-%% \subsection{Observation mode preferences -- for Web}
-%% \gdhelpid{prefPageObserveWebContextId}{Observation Mode Preferences}
-%% \input{Tasks/Preferences/obsprefsweb}
-
-
-\subsection{\gdcase{} diagram preferences}
-\gdhelpid{prefPageTCDGeneralContextId}{Test Case Diagram Preferences}
-\label{TasksPrefsModel}
-\input{Tasks/Preferences/diagramprefs}
-
\subsection{Test result preferences}
\gdhelpid{prefPageTestResultContextId}{Test Result Preferences}
+\gdhelpid{testResultSummaryViewContextId}{Test Result Summary View}
\label{testresprefs}
\input{Tasks/Preferences/testresultprefs}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/appearance.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/appearance.tex
deleted file mode 100644
index acd96b249..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/appearance.tex
+++ /dev/null
@@ -1,28 +0,0 @@
-\index{Preferences!Appearance}
-\index{Appearance!Preferences}
-\label{appearanceprefs}
-
-
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics[width=12.5cm]{Tasks/Preferences/PS/appearanceprefs}
-\caption{Appearance Preference Dialog}
-\label{appearanceprefs}
-\end{center}
-\end{figure}
-
-\begin{enumerate}
-\item You can opt to color-coordinate browsers, editors and views which are related to each other.
-\item If you want to color-coordinate, you can choose your color scheme.
-
-\bxname{Execution} refers to the \gdtestsuitebrowser{}, the \gdtestsuiteeditor{} and the \gdpropview{}, \gdcompnamesview{} and \gddatasetsview{} for this editor.
-
-\bxname{Specification} refers to the \gdtestcasebrowser{}, the \gdtestcaseeditor{} and the \gdpropview{}, \gdcompnamesview{} and \gddatasetsview{} for this editor.
-\end{enumerate}
-
-
-
-
-
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/dbprefs.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/dbprefs.tex
new file mode 100644
index 000000000..fb3175eb1
--- /dev/null
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/dbprefs.tex
@@ -0,0 +1,27 @@
+
+\index{Preferences!Database connection}
+\index{Database!Preferences}
+
+
+You can find the \gddb{} connection preference page under:\\
+\bxname{Test-\gddb{} Connections}\\
+in the preferences dialog.
+
+When you start \app{} for the first time, it is automatically configured to use an embedded \gddb{}. If this is the only \gddb{} configured, then the \gddb{} login is performed automatically.
+
+In this preference page, you can configure other \gddb{} connections for your productive \gddb{}. We do not recommend using the embedded \gddb{} for productive use of \app{}.
+
+
+\subsubsection{Adding, editing and removing \gddb{} configurations}
+
+To add a new \gddb{} for use with \app{}:
+
+\begin{enumerate}
+\item In the \gddb{} Connections preference page, click \bxcaption{Add}.
+\item In the dialog that appears, enter a meaningful configuration name.
+\item Select the type of \gddb{} that this configuration is for.
+\bxtipp{\app{} is thoroughly tested with Oracle. PostGreSQL and MySQL have been successfully tried out with \app{}, but we cannot guarantee their usage in productive environments.}
+\item Based on the \gddb{} type you choose, you must enter more details about the \gddb{} connection. Speak to your \gddb{} administrator if you are unsure of the connection details.
+\end{enumerate}
+
+You can edit and delete \gddb{} configurations using the buttons in the \gddb{} Connections preference page.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/diagramprefs.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/diagramprefs.tex
deleted file mode 100644
index 0fab3fea0..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/diagramprefs.tex
+++ /dev/null
@@ -1,69 +0,0 @@
-\index{Preferences!Test Case Diagram}
-\index{Test Case Diagram!Preferences}
-
-In the \gdcase{} diagram preferences page (\bxfigref{diagramprefs}), you can configure:
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics[width=12.5cm]{Tasks/Preferences/PS/diagramprefs}
-\caption{Diagram Preference Dialog}
-\label{diagramprefs}
-\end{center}
-\end{figure}
-
-\begin{description}
-\item [Connector handles:]{When this option is checked, you will see the connection arrows to add notes when an element is selected in your model. Click on a connector and drag to create a new note.}
-\item [Pop up bars:]{When this option is checked, you will see a pop-up with the options to add parameters and \gdcase{} referenced when an element is selected in your model. Clicking on the \bxname{add parameter} or the \bxname{add \gdcase{} reference} icon will add the element you choose to the currently selected item. }
-\item [Animated layout:]{When this option is activated, the arrangement of the items in the diagram will be animated when you click the \bxcaption{Arrange} button in the toolbar. }
-\item [Animated zoom:]{When this option is activated, zooming into or out of the diagram will be animated. }
-\item [Anti-aliasing:]{Use this option with higher-performance machines to smooth the lines connecting elements in the model. Machines with lower performance should deactivate this option. }
-\end{description}
-
-\subsubsection{\gdcase{} diagram appearance preferences}
-\gdhelpid{prefPageTCDAppearanceContextId}{Test Case Diagram Appearance Preferences}
-On the appearance preference page for the \gdcase{} diagram, you can specify which colors should be used within the model, for text and lines in the notes and in general.
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics[width=12.5cm]{Tasks/Preferences/PS/diagramappearanceprefs}
-\caption{Diagram Appearance Preference Dialog}
-\label{diagramappearanceprefs}
-\end{center}
-\end{figure}
-
-\subsubsection{\gdcase{} diagram connections preferences}
-\gdhelpid{prefPageTCDConnectionsContextId}{Test Case Diagram Connections Preferences}
-Use this preference page to specify how you would like the connections to appear in your model.
-\begin{description}
-\item [Oblique]{displays the connectors as direct, straight lines between the connected elements. }
-\item [Rectilinear]{displays connecting lines at right angles between the connected elements.}
-\end{description}
-
-
-\subsubsection{\gdcase{} diagram printing preferences}
-\gdhelpid{prefPageTCDPrintingContextId}{Test Case Diagram Printing Preferences}
-If you are planning on printing your \gdcase{} model, you can configure the print preferences in this page. For example, you can set the page orientation to portrait or landscape and use the context-sensitive menu in the model to view the page boundaries for your chosen orientation.
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics[width=12.5cm]{Tasks/Preferences/PS/diagramprintingprefs}
-\caption{Diagram Printing Preference Dialog}
-\label{diagramprintingprefs}
-\end{center}
-\end{figure}
-
-\subsubsection{\gdcase{} diagram rulers and grid preferences}
-\gdhelpid{prefPageTCDRulersContextId}{Test Case Diagram Rulers and Grid Preferences}
-In this preference page, you can specify whether you want to see the rulers and the grid for new diagrams. In the ruler settings, you can also specify the ruler units as centimeters, inches or pixels.
-
-Within the grid options, you can choose whether elements should snap to the grid (\bxname{snap to grid}), or to each other (\bxname{snap to shape}). The snap to shape option displays a horizontal or vertical line when an element is moved close to another element. The line can be used to line elements up with each other.
-
-The grid spacing can also be altered to decrease or increase the size of the grid blocks.
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics[width=12.5cm]{Tasks/Preferences/PS/diagramrulersprefs}
-\caption{Diagram Rulers and Grids Preference Dialog}
-\label{diagramrulersprefs}
-\end{center}
-\end{figure}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/editor.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/editor.tex
index f0bc5a228..864ca7d77 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/editor.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/editor.tex
@@ -12,6 +12,6 @@
\end{figure}
-Choose whether you want items (\gdcases{} and \gdsteps{}) to be placed at the bottom of the tree or after the selected item when you use the \bxname{add} option.
+In the \bxname{Test - Editors} preferences, you can choose whether you want items (\gdcases{} and \gdsteps{}) to be placed at the bottom of the tree or after the selected item when you use the \bxname{add} option.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/gdprefs.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/gdprefs.tex
index 0ce4a4856..6dfe42559 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/gdprefs.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/gdprefs.tex
@@ -8,8 +8,8 @@
% User documentation
% copyright by BREDEX GmbH 2004
% --------------------------------------------------------
-\index{Preferences!GUIdancer}
-\index{GUIdancer!Preferences}
+\index{Preferences!Test}
+\index{Test!Preferences}
\label{gdprefs}
\begin{figure}[h]
@@ -20,17 +20,19 @@
\end{center}
\end{figure}
- From this page, you can configure your preferences for:
+ In the preferences dialog, select \bxname{Test} from the tree on the left hand side.
+
+From this page, you can configure your preferences for:
\begin{description}
\item [Auto-scrolling and -expanding:]{When the checkbox is marked, the views and browsers in \app{} automatically scroll in the direction you move the mouse when you are dragging and dropping. Trees will also be automatically expanded when you hover over them while dragging items.}
-\item [Minimizing \app{}:]{When the checkbox is marked, \app{} is automatically minimized when test execution begins. This is useful if you are letting tests run on the same machine you are specifying on.}
+\item [Minimizing the \ite{}:]{When the checkbox is marked, \app{} is automatically minimized when test execution begins. This is useful if you are letting tests run on the same machine you are specifying on.}
\item [\gdaut{} confirmation dialog:]{When the checkbox is marked, a dialog appears to check if you are sure when you click the \bxcaption{stop \gdaut{}} button.}
\item [Original \gdcase{} name:]{When the checkbox is activated, you can see the original name of a referenced \gdcase{} in brackets behind a new name you enter for the \gdcase{}. This can help you to see and search for \gdcases{} you have reused. }
\item[\gdstep{} information:]{When this checkbox is activated, you see the details about the \gdstep{} (the component name and type, and the action) in square brackets behind the \gdstep{} name. If you do not want to see these details, you can deactivate this checkbox.}
-\item[Show referenced children:]{When this option is not active, you can only see referenced parent \gdcases{} in the \gdtestcasebrowser{}. The referenced \gdcases{} contained in these \gdcases{} are not displayed. This action can be useful if you want to improve the speed of working with the \app{} client.}
-\item [Switching to the Execution perspective:]{When the test begins, \app{} can automatically change to the Execution perspective. You can choose to always be asked, to always change, or to never change. }
+\item[Show referenced children:]{When this option is not active, you can only see referenced parent \gdcases{} in the \gdtestcasebrowser{}. The referenced \gdcases{} contained in these \gdcases{} are not displayed. This action can be useful if you want to improve the speed of working with the \ite{}.}
+\item [Switching to the \execpersp{}:]{When the test begins, \app{} can automatically change to the \execpersp{}. You can choose to always be asked, to always change, or to never change. }
\item [Data files location:]{You can specify a location where external data files (e.g. Excel files) are held, or use the workspace directory as the base location. }
-\bxtipp{The advantage of using the workspace as a location for your data files is that you can view these in the navigator view directly in \app{}. Windows users can even open Excel files in \app{} using the In-Place editor.}
+\bxtipp{The advantage of using the workspace as a location for your data files is that you can view these in the navigator view directly in the \ite{}. Windows users can even open Excel files from the \ite{} using the In-Place editor.}
\end{description}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/keys.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/keys.tex
index 983fd427f..bc50797eb 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/keys.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/keys.tex
@@ -1 +1 @@
-In the \bxname{General} preferences, you can select the \bxname{Keys} option to be able to edit the key binding for shortcuts in \app{}.
+In the \bxname{General} preferences, you can select the \bxname{Keys} option to be able to edit the key binding for shortcuts in \app{}. Here, you can create your own shortcuts or alter the current shortcuts.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/obsprefsweb.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/obsprefsweb.tex
deleted file mode 100644
index 414848ffa..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/obsprefsweb.tex
+++ /dev/null
@@ -1,12 +0,0 @@
-\index{Preferences!Observation Mode Web}
-\index{Observation Mode!Preferences}
-
-On this preference page, you can configure the key combinations to observe normal actions and actions of the application component in the observation mode for web applications.
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics[width=12.5cm]{Tasks/Preferences/PS/obsprefsweb}
-\caption{Observation Mode for Web Preference Dialog}
-\label{obsprefsweb}
-\end{center}
-\end{figure}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/omprefs.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/omprefs.tex
index 8b0d7a5db..38e65d337 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/omprefs.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/omprefs.tex
@@ -26,10 +26,11 @@
\end{center}
\end{figure}
+You can access the object mapping preferences from \bxname{Test - Object Mapping} in the preferences dialog.
\begin{enumerate}
-\item Select whether you want to show how many nodes are contained in each category in the \gdomeditor{}.
+\item Select whether you want \app{} to display how many nodes are contained in each category in the \gdomeditor{}.
\item Choose which keystrokes or mouse buttons you want to use to collect components in the \gdomm{}.
-\item Configure a keystroke to refresh a web application. This option can help with dynamic web \gdauts{}. Refreshing the components in the \gdaut{} allows \app{} to find new components added since the last refresh. There is also a \gdstep{} you can use to achieve the same effect in your tests.
+%\item Configure a keystroke to refresh a web application. This option can help with dynamic web \gdauts{}. Refreshing the components in the \gdaut{} allows \app{} to find new components added since the last refresh. There is also a \gdstep{} you can use to achieve the same effect in your tests.
\end{enumerate}
\bxtipp{If your \gdaut{} does not accept keystrokes, set the object collection preference to a mouse button combined with a modifier key.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/serverConfigPrefPage.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/serverConfigPrefPage.tex
index 021800ab4..8dbaf28f6 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/serverConfigPrefPage.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/serverConfigPrefPage.tex
@@ -14,6 +14,10 @@
\index{Add!AUT Agent}
\index{AUT Agent!Add}
+You can find the \gdagent{} preference page under:\\
+\bxname{Test-\gdagent{}}\\
+in the preferences dialog.
+
\begin{enumerate}
\item In the \gdagent{} preference page, you can add, edit and delete \gdagent{}s and port numbers.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/testresultprefs.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/testresultprefs.tex
index 0b362314e..346008f1e 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/testresultprefs.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Preferences/testresultprefs.tex
@@ -12,7 +12,7 @@
\index{XML and HTML Result Reports}
\index{Results!XML and HTML Reports}
-
+You can open the test result preference page by selecting \bxname{Test - Test Results} from the preference dialog.
\begin{figure}[h]
\begin{center}
@@ -27,9 +27,10 @@
The \gdtestresultview{} follows the test execution and shows which \gdsteps{} were successful and which failed.
\item Choose whether you want to track the test execution progress in the \gdtestresultview{}. When this option is activated, the \gdtestresultview{} scrolls to follow the test progress.
+\item Choose whether you want \app{} to automatically create a screenshot when a test encounters an error. Screenshots are automatically saved in the \gddb{} and can be viewed using the \gdimgview{} when you select the failed \gdstep{} in the \gdtestresultview{}.
\item Choose whether you want to create HTML and XML reports for each execution. When you activate this choice, decide whether you want full reports or just the errors to be shown. Enter a directory for the reports.
-\item Choose whether you want \app{}to automatically create a screenshot when a test encounters an error. Screenshots are automatically saved in the \gddb{} and can be viewed using the \gdimgview{} when you select the failed \gdstep{} in the \gdtestresultview{}.
-\item Decide whether you want all test runs or no test runs to be marked as relevant, or whether you want to be prompted each time. If a test run is marked as non-relevant, then it will not be included for any generated BIRT reports, nor will it be exported when the \gdproject{} is exported.
+\item Decide whether you want all test runs or no test runs to be marked as relevant, or whether you want to be prompted each time. Non-relevant test results are not exported with the \gdproject{}.
+\item Enter the amount of days that test result summaries should be displayed for. This gives you a better overview of the most recent results in the \gdtestsummaryview{}.
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/CONTENT.tex
index 0c41170d3..e3d84f311 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/CONTENT.tex
@@ -35,8 +35,6 @@
\subsection{Observing tests in Java \gdauts{}}
\input{Tasks/Recording/observejava}
-%% \subsection{Observing tests in HTML \gdauts{}}
-%% \input{Tasks/Recording/observeweb}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/entering.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/entering.tex
deleted file mode 100644
index 35ba32ce1..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/entering.tex
+++ /dev/null
@@ -1,47 +0,0 @@
-% $Id: entering.tex 2762 2006-08-24 15:05:41Z $
-% Local Variables:
-% ispell-check-comments: nil
-% Local IspellDict: american
-% End:
-% --------------------------------------------------------
-% User documentation
-% copyright by BREDEX GmbH 2005
-% --------------------------------------------------------
-% this command can be inserted multiple times
-%\gdhelpid{}
-%
-%\begin{gddescription}
-%\end{gddescription}
-%
-%\begin{gdlist}
-% use the \item command for single steps
-%\end{gdlist}
-% change <PATH> to the same directory, file is located in
-% change <FILE> to the same filename you are editing
-%\bxinput{<PATH>/Links/<FILE>}
-%
-% other usefull commands are
-% \bxtipp{} to create a hint
-% \bxwarn{} to describe a warning
-\index{Observation Mode}
-\label{observeprereq}
-\begin{itemize}
-\item Before observing, you must:
-\begin{enumerate}
-\item Define and configure an \gdaut{} \bxpref{Defineaut}.
-\item Create a \gdsuite{} \bxpref{TSeditor}.
-\item Choose an \gdaut{} for the \gdsuite{} \bxpref{confsuite}.
-\item Make sure that the \gdaut{} for your \gdsuite{} supports the current working language.
-\item Make sure that the current working language is the language you want to observe in.
-\item Connect to the \gdagent{} \bxpref{connectserv}.
-\item Start the \gdaut{} \bxpref{startaut}.
-\end{enumerate}
-\item You can then start the observation mode \bxpref{startobs}.
-\end{itemize}
-
-
-
-
-
-
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observejava.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observejava.tex
index 17b934111..f8e3892bf 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observejava.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observejava.tex
@@ -6,7 +6,7 @@
\begin{enumerate}
\item In Java \gdauts{} (Swing and SWT/RCP) the observation mode will automatically record your actions in the user interface. Each action is created as a \gdstep{} in the \gdtestcaseeditor{} for this observed \gdcase{}.
-\bxtipp{See the section later on performing check actions in the observation mode for Java \bxpref{TasksObsCheckJava}.}
+\bxtipp{See the section later on performing check actions in the observation mode \bxpref{TasksObsCheckJava}.}
\item You can also see which actions have been recorded in the console (\bxfigref{obsconsole}).
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observeweb.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observeweb.tex
deleted file mode 100644
index d7b5931aa..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/observeweb.tex
+++ /dev/null
@@ -1,38 +0,0 @@
-\label{TasksObserveWeb}
-The observation mode for HTML \gdauts{} involves hovering over the component you want to record an action on and pressing a key combination to execute an action on this component:
-\begin{itemize}
-\item Press \bxkey{Ctrl+Shift+A} to map that component.
-\item Press \bxkey{Ctrl+Shift+S} to map the application component.
-\end{itemize}
-
-Supported components are marked with red borders (\bxfigref{redborders}).
-
-\begin{figure}[h]
-\begin{center}
-\includegraphics{Tasks/Recording/PS/redborders}
-\caption{Red borders in the observation mode}
-\label{redborders}
-\end{center}
-\end{figure}
-
-In the dialog which appears, choose the action you want to execute on this component.
-
-Once you have done this, you can:
-\begin{enumerate}
-\item Enter the parameters for the action, as prompted by the dialog box.
-\bxtipp{You can only enter concrete parameter values in this dialog.}
-\item Click \bxcaption{OK} in the dialog.
-\item The action you just specified will be carried out.
-\item In the \gdtestcaseeditor{} for the \gdcase{} you are observing, the \gdstep{} you just observed will appear.
-\item In the \gdpropview{}, you will see that the \bxname{component} name field contains a name generated by \app{}. This component name is assigned to the technical name for the component in the \gdomeditor{}.
-\bxtipp{If you change the component name, remember that you will need to reassign your new name to the technical name in the \gdomeditor{}. }
-\end{enumerate}
-
-Once you have finished observing your \gdcase{}, stop the observation mode by
-selecting the \bxcaption{stop observing} button on the toolbar.
- \gdmarpar{../../../share/PS/stopcam}{ stop observation}
-\bxtipp{When you are observing, remember that your tests will be more flexible and maintainable if you make the \gdcases{} small, reusable units. }
-
-Save the changes in the editor.
-
-%checks in the observation mode
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/startobs.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/startobs.tex
index 786fd5676..1c3a92d3b 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/startobs.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/startobs.tex
@@ -22,9 +22,9 @@ To be able to observe \gdsteps{}, you must:
\begin{itemize}
\item define an \gdaut{} \bxpref{Defineaut}
\bxtipp{Only Java \gdauts{} can use the observation mode. }
-\item configure an \gdaut{} \bxpref{configuringaut} is you want to start it via \app{}.
+\item configure an \gdaut{} \bxpref{configuringaut} if you want to start it via \app{}.
\item set the working language to the language you want to observe in.
-\item start the \gdaut{} you want to observe from \bxpref{startaut} (either via a configueation \bxpref{configuringaut} or using the \bxname{gdrun} command \bxpref{gdrun}).
+\item start the \gdaut{} you want to observe from \bxpref{startaut} (either via a configuration \bxpref{configuringaut} or using the \bxname{autrun} command \bxpref{autrun}).
\end{itemize}
Once you have completed these steps, you can select the \bxcaption{observe \gdcase{}} button
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/tips.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/tips.tex
index f9987cd8a..4095cecaa 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/tips.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Recording/tips.tex
@@ -1,6 +1,6 @@
\index{Observation Mode!Tips}
-We have designed the \app{} observation mode to help you get started with your tests and to help you understand what sort of user actions correspond to \app{} actions.
+We have designed the observation mode to help you get started with your tests and to help you understand what sort of user actions correspond to \app{} actions.
\app{} is first and foremost a keyword-driven tool, and the library of \gdcases{} installed with \app{} means that you have various benefits over simple recording:
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
index 972babf13..02dbb961a 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
@@ -126,6 +126,7 @@ For more details about individual tasks, read the \bxref{Concepts}
\section{Dealing with errors in tests: \gdehandlers{}}
\gdhelpid{guidancerSpecTestCaseEditorContextId}{Test Case Editor}
\gdhelpid{eventHandlerAddContextId}{Event Handlers}
+\gdhelpid{testExecViewContextId}{Test Suite Browser}
\label{customizedehandler}
\input{Tasks/Eventhandlers/CONTENT}
@@ -141,10 +142,7 @@ For more details about individual tasks, read the \bxref{Concepts}
\gdhelpid{testSpecificationViewContextId}{Test Case Browser}
\input{Tasks/Recording/CONTENT}
-\clearpage
-\section{Using the modeling perspective}
-\input{Tasks/Modelling/CONTENT}
\clearpage
\section{Working with the \gdprobview}
@@ -170,11 +168,11 @@ For more details about individual tasks, read the \bxref{Concepts}
\clearpage
-\section{Using the command line client}
+\section{Using the test executor}
\gdhelpid{problemViewContextId}{Problem View}
\input{Tasks/Commandline/CONTENT}
-\section{Using the GUIdancerDBTool client}
+\section{Using the dbtool client}
\gdhelpid{problemViewContextId}{Problem View}
\label{DBTool}
\input{Tasks/DBTool/CONTENT}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Searching/searchdialog.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Searching/searchdialog.tex
index 63ebbf6ab..4426c926a 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Searching/searchdialog.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Searching/searchdialog.tex
@@ -7,7 +7,7 @@ The search dialog allows you to search the \textbf{current \gdproject{} in the
\item Keywords \bxpref{TasksSearchKeywords} (\gdcases{}, \gdsteps{}, \gdsuites{}, \gdjobs{} and categories).
\item Test data used in \gdcases{} or central test data sets \bxpref{TasksSearchData}.
\item Files in the workspace \bxpref{TasksSearchFiles}.
-\item Tasks in the repository \bxpref{TasksSearchTasks}.
+%\item Tasks in the repository \bxpref{TasksSearchTasks}.
\end{itemize}
@@ -65,13 +65,13 @@ On the third tab of the search dialog, you can search for and in files contained
Enter the term you wish to search for and click \bxcaption{Search} to start the search. The results are shown in the \gdsearchresultview{} \bxpref{TasksSearchResultView}.
-\subsubsection{Searching for tasks in Mylyn}
-\gdhelpid{testSpecificationViewContextId}{Test Case Browser}
-\gdhelpid{testExecViewContextId}{Test Suite Browser}
-\label{TasksSearchTasks}
+%% \subsubsection{Searching for tasks in Mylyn}
+%% \gdhelpid{testSpecificationViewContextId}{Test Case Browser}
+%% \gdhelpid{testExecViewContextId}{Test Suite Browser}
+%% \label{TasksSearchTasks}
-On the fourth tab of the search dialog, you can search for tasks in any repositories you have referenced in the \gdproject{}.
+%% On the fourth tab of the search dialog, you can search for tasks in any repositories you have referenced in the \gdproject{}.
-You can use this search if you are using Mylyn in \app{}, and are using a task repository to manage your Mylyn tasks.
+%% You can use this search if you are using Mylyn in \app{}, and are using a task repository to manage your Mylyn tasks.
-Click \bxcaption{Search} to start the search. The results are shown in the \gdsearchresultview{} \bxpref{TasksSearchResultView}.
+%% Click \bxcaption{Search} to start the search. The results are shown in the \gdsearchresultview{} \bxpref{TasksSearchResultView}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/AUTstop.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/AUTstop.tex
index 744e5bc85..dd9cc9de4 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/AUTstop.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/AUTstop.tex
@@ -11,9 +11,9 @@
\index{Stop!AUT}
\begin{enumerate}
\item When you stop the \gdagent{}, any \gdauts{} that were connected to this \gdagent{} are closed.
-\item \gdauts{} which were started from a \app{} configuration are automatically closed when the test execution via the command line client stops.
-\item To stop the \gdaut{} manually, select the \gdaut{} you want to stop from the \app{}unautview{} and then click the {Stop \gdaut{}} button.
+\item \gdauts{} which were started from a configuration are automatically closed when the test execution via the test executor stops.
+\item To stop the \gdaut{} manually, select the \gdaut{} you want to stop from the \gdrunautview{} and then click the {Stop \gdaut{}} button.
\gdmarpar{../../../share/PS/stopAUT}{ stop \gdaut{}}
\item A dialog will appear to ask you if you are sure you want to stop the \gdaut{}. Click \bxcaption{yes}.
-\item You can opt to not see this dialog on the \app{} preference page \bxpref{gdprefs}.
+\item You can opt to not see this dialog in the preferences \bxpref{gdprefs}.
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/TSstop.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/TSstop.tex
deleted file mode 100644
index b2808d748..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/TSstop.tex
+++ /dev/null
@@ -1,19 +0,0 @@
-% $Id: TSstop.tex 4493 2007-02-08 09:58:18Z mike $
-% Local Variables:
-% ispell-check-comments: nil
-% Local IspellDict: american
-% End:
-% --------------------------------------------------------
-% User documentation
-% copyright by BREDEX GmbH 2004
-% --------------------------------------------------------
-\index{Stop!Test Suite}
-\index{Test Suite!Stop}
-
-When a \gdsuite has finished, it stops automatically.
-
-To stop a \gdsuite before it has finished, select the
- \bxcaption{Stop \gdsuite} button
-\gdmarpar{../../../share/PS/stop}{ stop \gdsuite}
-on the toolbar.
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/application.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/application.tex
index 1b64e1882..ebfb107ba 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/application.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Termination/application.tex
@@ -28,7 +28,7 @@
\index{AUT Agent!Stop}
Once the \gdsuite{}, \gdaut{} and \gdagent{} have been stopped or disconnected,
-make sure any changes are saved and select: \\ \bxmenu{Project}{Exit}{}.
+make sure any changes are saved and select: \\ \bxmenu{File}{Exit}{}.
\subsection{Stopping the \gdagent}
\gdhelpid{problemViewContextId}{Problem View}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testcases/edit.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testcases/edit.tex
index 9f4d85e40..7972c807f 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testcases/edit.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testcases/edit.tex
@@ -8,7 +8,9 @@ From the \gdtestcaseeditor{}, you can edit a \gdcase{}. You can:
\item add and edit \gdsteps{} \bxpref{specsteps}.
\item rename the \gdcase{} \bxpref{TasksBrowserRename} or the \gdcases{} it contains \bxpref{TasksEditorRename}.
\item add a comment to the \gdcase{} \bxpref{TasksEditorAddComment}.
-\item add, edit or translate data for the \gdcase{} \bxpref{TasksDataSetsView}.
+\item add, edit or translate data for the \gdcase{} \bxpref{TasksDataSetsView}.
+\item extract \gdcases{} from within this \gdcase{} to make reusable modules \bxpref{TasksEditorExtract}.
+\item deactivate specific \gdcases{} in this \gdcase{} so they are ignored during execution \bxpref{TasksEditorDeactivate}.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/CONTENT.tex
index 7c0f61969..28f3e5e15 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/CONTENT.tex
@@ -1,9 +1,9 @@
-%change all references to new ones, delete old files
\subsection{Data types and entering data for \gdcases{}}
\gdhelpid{guidancerPropertiesViewContextId}{Properties View}
\gdhelpid{guidancerSpecTestCaseEditorContextId}{Test Case Editor}
\gdhelpid{guidancerDataSetViewContextId}{Data Sets View}
+\gdhelpid{guidancerCentralTestDataEditorContextId}{Central Test Data}
\label{TasksDataTypes}
\input{Tasks/Testdata/data}
@@ -20,6 +20,7 @@
\subsection{Using the edit parameters dialog to add, edit and delete references}
\gdhelpid{guidancerPropertiesViewContextId}{Properties View}
\gdhelpid{editParametersDialogContextId}{Editing Parameters}
+\gdhelpid{guidancerCentralTestDataEditorContextId}{Central Test Data}
\label{TasksTestdataEditParams}
\input{Tasks/Testdata/editparams}
@@ -43,6 +44,7 @@
\subsection{Using central data sets}
\gdhelpid{guidancerPropertiesViewContextId}{Properties View}
+\gdhelpid{guidancerCentralTestDataEditorContextId}{Central Test Data}
\label{TasksCentralData}
\input{Tasks/Testdata/central}
@@ -51,13 +53,15 @@
\label{TasksExcel}
\input{Tasks/Testdata/excel}
-\subsection{Using the \gddatasetsview{} to enter parameter values and to translate data}
+\subsection{Using the \gddatasetsview{} to enter data loops and to translate data}
\gdhelpid{guidancerDataSetViewContextId}{Data Sets View}
+\gdhelpid{guidancerCentralTestDataEditorContextId}{Central Test Data}
\label{TasksDataSetsView}
\input{Tasks/Testdata/datasets}
\subsection{Special parameters: empty strings and the escape character}
\gdhelpid{guidancerPropertiesViewContextId}{Properties View}
+\gdhelpid{guidancerCentralTestDataEditorContextId}{Central Test Data}
\input{Tasks/Testdata/special}
\subsection{Overwriting data for \gdcases{} and \gdsuites{}}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/central.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/central.tex
index 1152f0e48..c7c2ab9b0 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/central.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/central.tex
@@ -41,7 +41,7 @@ Once you have created a central test data set \bxpref{TasksCentralDataCreate}, y
\item Open the edit parameters dialog for the central data set by right-clicking on the data set in the \gddataeditor{} and selecting \bxmenu{Edit parameters}{}{} from the context-sensitive menu.
\item In the dialog, you can see any parameters you have already added for this data set, and what type of parameters they are.
\item Use the \bxcaption{Add} button to create a new parameter for the data set.
-\item Enter a name for the parameter and select the type of parameter it should be (e.g. String, Integer). The type of parameter it should be will depend on which actions are using it. A list of actions and their parameters (and types) is available in the reference manual.
+\item Enter a name for the parameter and select the type of parameter it should be (e.g. String, Integer, ...). The type of parameter it should be will depend on which actions are using it. A list of actions and their parameters (and types) is available in the reference manual (\bxextref{\gdrefman}{ref,actparam}).
\bxtipp{Names for referenced parameters may only consist of letters, numbers and underscores. You cannot use spaces.}
\item You can also change the order the parameters appear in, edit their types and names, and delete them completely using this dialog.
@@ -64,7 +64,7 @@ from the \gdtestsuitebrowser{}.
\item In the \gddatasetsview{}, make sure the language in the combo box on the right is the right language for your data.
\item Select \bxcaption{Add} to add a row.
\item Enter the values for the parameters in the row.
-\bxtipp{You cannot currently add referenced parameters in the \gddatasetsview{} for a central test data set.}
+\bxtipp{You cannot add referenced parameters (i.e. reference names preceded by the equals sign) in the \gddatasetsview{} for a central test data set.}
\item Use the buttons in the \gddatasetsview{} to add more rows, delete rows and insert rows above the currently selected row.
\end{enumerate}
@@ -77,9 +77,10 @@ You can reuse a central test data set in a \gdcase{} to provide the concrete dat
\begin{enumerate}
\item In the \gdpropview{} for the \gdcase{}, enter the name of the central test data set you want to use in the \bxname{Central Test Data Set} field.
-\bxtipp{Press \bxkey{Ctrl+Space} to see a list of possible data sets for this \gdcase{}.}
+\bxtipp{Press \bxkey{Ctrl+Space} to see a list of possible data sets for this \gdcase{}. You will only be shown data sets that contain the correct parameters with the correct types.}
\item When you have entered a central test data set, then the \gdpropview{} shows \bxname{central test data set} as the data type. You will see the data from the central test data set in read-only form in the \gddatasetsview{}.
\bxtipp{If data is missing from the central test data set, you will receive the error that test data is incomplete for any \gdsuites{} this \gdcase{} is used in.}
\item You can delete the central test data set used by removing it from the \bxname{central test data set} field. The data type reverts to \bxname{local data}.
For more information on the data sources, see the earlier section \bxpref{TasksDataSources}.
+\bxtipp{You can use central test data sets that contain more parameters than your \gdcase{}. For example, if your \gdcase{} requires the parameters \bxshell{NAME, ADDRESS} and your central test data set contains \bxshell{NAME, ADDRESS, POSTCODE}, you can still use the central test data set.}
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/concatenate.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/concatenate.tex
index f9cfdc65a..7f0cd2d06 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/concatenate.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/concatenate.tex
@@ -17,8 +17,8 @@ To combine different types of parameter to make one value, you must write them i
\item Variable names must also be written with curly brackets around them:\\
\bxshell{\$\{VAR\_NAME\}}
\item Concrete values are written as normal.
-\item For example, to check a file name which has the format \bxname{X\_currentdate\_filenumber}, you could enter a parameter thus:\\
-\bxshell{X\_=\{DATE\}\_\$\{FILENUMBER\}}\\
+\item For example, to check a file name which has the format \bxname{test\_projectname\_filenumber}, you could enter a parameter thus:\\
+\bxshell{test\_=\{PROJECTNAME\}\_\$\{FILENUMBER\}}\\
The date value would come from a reference, and the file number from a variable read from the \gdaut{}.
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/datasets.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/datasets.tex
index 0cbe04bb2..c1eabf3da 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/datasets.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/datasets.tex
@@ -36,9 +36,6 @@ You can add data for other languages supported by your \gdaut{} by changing the
\bxtipp{You can add supported languages in the \gdproject{} properties dialog \bxpref{projectproperties}.}
-%\bxtipp{If you are entering data via the \gdtestcasebrowser{}, you can add data for all of the \gdproject{} languages.
-%If you are entering data via the \gdtestsuitebrowser{}, you can only add data for languages supported by the \gdaut{} chosen for the \gdsuite{}. }
-
The other combo boxes are there to help you see the \gddatasetsview{} in different ways. You can see all the data for one parameter, for one data set or for one language.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/excel.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/excel.tex
index 355780fea..1bd7861eb 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/excel.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/excel.tex
@@ -11,7 +11,7 @@ The path to the Excel file can be absolute or relative (if you have specified a
\item If you reuse this \gdcase{}, the Excel file you enter will be reused along with the \gdcase{}. When you reuse the \gdcase{}, you can choose whether you leave this file or change it for another one.
\bxtipp{If you store your Excel files in your workspace, you will be able to open these directly in \app{} from the navigator view using the in-place editor. }
-\item A \gdcase{} you have added an Excel file to is marked with a small Excel icon in the browsers to help you find it more easily later.
+\item A \gdcase{} with an Excel file as data is marked with a small Excel icon in the browsers to help you find it more easily later.
\bxwarn{Please note that the Excel file is read at the start of the test execution. Any changes to the file after this will not affect the test data. For information on using the date function in Excel, see the section later \bxpref{exceltoday}.}
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/overwritedata.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/overwritedata.tex
index b0d618a2b..8fc586efc 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/overwritedata.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/overwritedata.tex
@@ -20,7 +20,7 @@ Reusing \gdcases{} happens in two ways:
\item You can enter parameter values here or reference the parameters again. They would then become parameters of the \bxname{parent} \gdcase{}.
-\bxtipp{If you enter values here, you can see a yellow diamond next to the \bxname{parameter value} field. This means that the original data have been overwritten. The data source changes to read \bxname{local \gdcase{}}}
+\bxtipp{If you enter values here, you can see a yellow diamond next to the \bxname{parameter value} field. This means that the original data have been overwritten. The data source changes to \bxname{local \gdcase{}}}
If you add references here, you will be able to enter or overwrite data when you reuse the parent \gdcase{}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/special.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/special.tex
index 9b921a30d..d8b376464 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/special.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/special.tex
@@ -10,7 +10,7 @@ You can use this with the \bxname{equals}, \bxname{matches} or \bxname{simple ma
You can also use '\verb+^$+' or '\verb+^\s*$+' with the operator \bxname{matches} to check that a text area is empty.
-%You can also use '\verb+^$+' with the operator \bxname{matches} to check that a text area is empty.
+You can also use '\verb+^$+' with the operator \bxname{matches} to check that a text area is empty.
\bxtipp{If a component looks empty, but entering an empty string doesn't work, it may be worth asking a developer what is actually in the component.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/variables.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/variables.tex
index 4574edc37..07b52a94e 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/variables.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/variables.tex
@@ -52,7 +52,7 @@ You will need to set environment variables which have the form:\\
\bxshell{GDUDV\_<variablename>}\\
-\bxname{GDUDV} stands for \bxcaption{\app{} user-defined variable}.
+%\bxname{GDUDV} stands for \bxcaption{\app{} user-defined variable}.
To use the variable in your tests, enter the variable name (everything after the underscore) preceded by a dollar sign. Do not enter the \bxcaption{GDUDV\_} part.
@@ -62,7 +62,7 @@ Your system administrator will be able to help you with operating-system specifi
-\subsubsection{Using the \app{}pre-defined test execution variables}
+\subsubsection{Using the \app{} pre-defined test execution variables}
\label{TasksPredefinedVariables}
\index{Variables!Pre-defined}
\index{Predefined Variables}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/CONTENT.tex
index eeae7e403..523ebf3e5 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/CONTENT.tex
@@ -9,6 +9,7 @@
% --------------------------------------------------------
\subsection{Prerequisites for test execution}
\gdhelpid{testExecViewContextId}{Test Suite Browser}
+\gdhelpid{runningAutsViewContextId}{Running AUTs View}
\input{Tasks/Testexecution/preparing}
\subsection{Connecting to the \gdagent}
@@ -30,8 +31,15 @@
\label{TasksStartExec}
\input{Tasks/Testexecution/TSstart}
-\subsection{Pausing the test execution when errors occur}
+\subsection{Interactive test analysis}
\gdhelpid{testExecViewContextId}{Test Suite Browser}
\gdhelpid{runningAutsViewContextId}{Running AUTs View}
\gdhelpid{testResultViewContextId}{Test Results View}
+\label{TasksPauseOnError}
\input{Tasks/Testexecution/pause}
+
+\subsection{Altering the speed of test execution}
+\gdhelpid{testExecViewContextId}{Test Suite Browser}
+\gdhelpid{runningAutsViewContextId}{Running AUTs View}
+\label{TasksExecSpeed}
+\input{Tasks/Testexecution/speed}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/TSstart.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/TSstart.tex
index cf2fde278..43bc9c60b 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/TSstart.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/TSstart.tex
@@ -28,14 +28,14 @@ To start a \gdsuite{} or a \gdjob{}, you must:
\begin{description}
-\item [Starting a \gdsuite{}:]{You can start a \gdsuite{} from the \gdtestsuitebrowser{} or from the \app{}unautview{}. Click on the arrow next to the \bxcaption{Start test execution} button and select a \gdsuite{} to start from the list.}
+\item [Starting a \gdsuite{}:]{You can start a \gdsuite{} from the \gdtestsuitebrowser{} or from the \gdrunautview{}. Click on the arrow next to the \bxcaption{Start test execution} button and select a \gdsuite{} to start from the list.}
\item [Starting a \gdjob{}:]{You can start a \gdjob{} from the \gdtestsuitebrowser{}. Click on the arrow next to the \bxcaption{start test execution} button and select a \gdjob{} to start from the list.}
\end{description}
\gdmarpar{../../../share/PS/startSuite}{ start test}
-\bxtipp{The amount of \gdsuites{} or \gdjobs{} in the list for the \bxcaption{start test} button depends on your selection. In the \app{}unautview{}, only \gdsuites{} for the currently selected \gdaut{} will be shown. In the \gdtestsuitebrowser{}, if you have selected a \gdsuite{} or a \gdjob{}, only the selected item will be startable. }
+\bxtipp{The amount of \gdsuites{} or \gdjobs{} in the list for the \bxcaption{start test} button depends on your selection. In the \gdrunautview{}, only \gdsuites{} for the currently selected \gdaut{} will be shown. In the \gdtestsuitebrowser{}, if you have selected a \gdsuite{} or a \gdjob{}, only the selected item will be startable. }
\subsubsection{Stopping a \gdsuite{} or \gdjob{}}
\index{Test!Stop}
@@ -65,5 +65,6 @@ The test stops automatically when it finishes or when an error occurs whose \gde
\gdmarpar{../../../share/PS/pause}{ pause test}
\item To continue with the test, press the \bxcaption{Pause test execution} button again.
+\bxtipp{You can opt to automatically pause the test execution when an error occurs via the toolbar \bxpref{TasksPauseOnError}.}
\bxwarn{If the client and \gdagent are installed on the same machine, moving the mouse will disrupt the test. }
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/pause.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/pause.tex
index 33dd4c301..a502b1ed1 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/pause.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/pause.tex
@@ -1,8 +1,21 @@
+\index{Pause on Error}
+\index{Continue without Event Handler}
+
+If you are executing tests interactively, you can use \app{} to help you analyze any errors that occur.
+
+\subsubsection{Pause on Error}
On the toolbar in the \app{} client, click the \bxcaption{Pause on Test Execution Errors} button
%TODO
%\gdmarpar{../../../share/PS/}{ pause test execution on error}
or press \bxkey{F9} to cause the test to pause when it encounters an error.
-You can use this option to monitor your tests interactively. Once you have examined the error, you can click the \bxcaption{pause test execution} button on the toolbar to continue the test \bxpref{PauseExec}.
-
\bxtipp{Failed \gdsteps{} that have a retry \gdehandler{} will not be paused unless the final retry fails.}
+
+\subsubsection{Continuing after an error}
+Once you have analyzed the error in the \gdaut{} or in the test specification, you have two options:
+
+\begin{description}
+\item [Continue with the \gdehandler{}:]{Press the \bxcaption{Pause test execution} button on the toolbar \bxpref{PauseExec} to continue with the test. This will result in a \gdehandler{} (either a default \gdehandler{} or one of your own) being activated.}
+\item [Continue without \gdehandler{}:]{Press the \bxcaption{Continue without \gdehandler{}} button or \bxkey{F8} to continue with the test \bxname{as if the failed \gdstep{} had been successful}. No \gdehandler{} is activated. This option is useful if the \gdehandler{} that would be activated would restart the \gdaut{} or exit the test, but you are either able to ignore the error for the moment or make changes in the \gdaut{} to ensure that the test will be able to continue. }
+\end{description}
+\bxwarn{Any changes you make to the test specification while the test is paused will not become valid until the next test execution start.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/preparing.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/preparing.tex
index 73edd1ddc..12e353fae 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/preparing.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/preparing.tex
@@ -35,7 +35,7 @@ To be able to start a test you must:
\item Choose an \gdaut{} for the \gdsuite{} \bxpref{confsuite}.
\item Set the working language to the language you want to execute the test in.
\item Connect to the \gdagent{} \bxpref{connectserv}.
-\item Start the \gdaut{} \bxpref{startaut} (either via \app{} or using the \bxname{gdrun} command).
+\item Start the \gdaut{} \bxpref{startaut} (either via \app{} or using the \bxname{autrun} command).
\item Complete object mapping \bxpref{objectmappingtasks}.
\item Make sure that your test data is complete in your \gdcases{}.
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/speed.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/speed.tex
new file mode 100644
index 000000000..c75191332
--- /dev/null
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/speed.tex
@@ -0,0 +1,11 @@
+\index{Test execution!Speed}
+\index{Speed of test execution}
+
+You can alter the speed of the test execution in two ways:
+
+\begin{description}
+\item [System settings:]{You can increase or decrease the speed of double clicks bia the system settings to increase or decrease the speed at which \app{} can work when executing tests. }
+\item [In \gdsuites{}:]{In the \bxname{step delay} field in the \gdpropview{} for a \gdsuite{}, you can add a delay in ms to a \gdsuite{} which should be left between the execution of each step. }
+\end{description}
+
+\bxwarn{When increasing the settings for double click speed, bear in mind that your \gdaut{} and the libraries it uses must be able to deal with the increased click speed. If you notice that your \gdaut{} is having timing problems related to the click speed, then you may have to reduce it.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/startaut.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/startaut.tex
index ac37e5de9..36f956982 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/startaut.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testexecution/startaut.tex
@@ -23,7 +23,7 @@ To start the \gdaut{}, you must:
\begin{itemize}
\item have defined an \gdaut{} \bxpref{Defineaut}
\item have connected to the \gdagent{} \bxpref{connectserv}
-\item if you want to start your \gdaut{} via \app{}, and not using the \bxname{gdrun} option, then you must have configured an \gdaut{} \bxpref{configuringaut}
+\item if you want to start your \gdaut{} via \app{}, and not using the \bxname{autrun} option, then you must have configured an \gdaut{} \bxpref{configuringaut}
\end{itemize}
\bxtipp{You can only start \gdauts{} via \app{} which support the current working language. Change the working language if necessary by selecting a language from the list next to the language button on the toolbar.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/CONTENT.tex
index 1de1c4049..6907ffd69 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/CONTENT.tex
@@ -15,14 +15,3 @@
\label{TestResSumView}
\input{Tasks/Testresults/summary}
-\subsection{Generating BIRT reports}
-\gdhelpid{testResultSummaryViewContextId}{Test Result Summary View}
-\input{Tasks/Testresults/generatebirt}
-
-\subsection{Writing your own BIRT reports}
-\gdhelpid{testResultSummaryViewContextId}{Test Result Summary View}
-\label{OwnBIRT}
-\input{Tasks/Testresults/ownbirt}
-
-\subsection{Showing BIRT reports in an external viewer}
-\input{Tasks/Testresults/external}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/external.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/external.tex
deleted file mode 100644
index 98dec8efb..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/external.tex
+++ /dev/null
@@ -1,5 +0,0 @@
-The \app{} BIRT reports are shown in an integrated BIRT report viewer.
-
-If you have a BIRT report viewer elsewhere (e.g. in a Tomcat server), then you can put the templates and the library into the external BIRT viewer on the server and view them without starting \app{}.
-
-For information on viewing BIRT reports in external viewers, please consult the BIRT documentation.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/generatebirt.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/generatebirt.tex
deleted file mode 100644
index 76a4043d9..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/generatebirt.tex
+++ /dev/null
@@ -1,32 +0,0 @@
-\begin{itemize}
-\item From the \gdtestsummaryview{}, you can generate reports of your tests using the BIRT reporting engine.
-\item \app{} offers a selection of example reports:
-\begin{description}
-\item[GUIdancerShort:]{This report shows a pie chart of the selected tests as an overview: how many were successful and how may failed. }
-\item [GUIdancerHistory:]{This report shows a graph of the percentage completion for the selected \gdsuites{} for the dates given. There is also a list of the \gdauts{}, \gdsuites{} and test runs.}
-\item [GUIdancerHistoryAbsolute:]{This report shows the same details as the GUIdancerHistory report, but instead of showing the test results in percentages, shows the actual amount of \gdsteps{} executed. It also shows the difference between expected and executed \gdsteps{}.}
-\item [Testresult:]{This report gives out the full test details up to the given nesting level.}
-\item [TestresultError:]{This report shows where errors in the selected tests occurred and displays any screenshots taken automatically alongside the results \bxpref{testresprefs}.}
-\item [GUIdancerFULL:]{The full report is a combination of the short reports and history reports. }
-\end{description}
-
-\item To start a report, click the arrow next to the \bxcaption{Create Report} button and select the report you want to generate.
-\gdmarpar{../../../share/PS/createBirtReport}{create BIRT report}
-
-\bxtipp{If you are not already connected to the \gddb{}, then a dialog will appear to create the connection \bxpref{tasksdblogin}. }
-
-\item The BIRT report viewer starts (the first time it starts it may take some time).
-\item The parameters for the report are displayed:
-\begin{description}
-\item [\gddb{} connection:]{The current \gddb{} connection, user and password are automatically placed into the field for the connection information.}
-\item [Selection:]{In this section, specify which time frame the report should be generated for (either from a specific date, or using the options \bxname{yesterday, now, last week} etc.) as well as for which \gdproject{}, \gdsuite{}, and the operating system. The details in the selection section are combined using \bxname{and}. SQL syntax can be used (e.g. \verb+%+ is used as a wildcard for any number of any characters, \verb+_+ is used as a wildcard for one character). }
-\item [Detail Selection:]{For the Testresult and TestresultError reports, you must also specify the nesting level (how many levels in the hierarchy should be shown) and the ID of the test run you want to generate the report for. The test run ID for each run can be seen in the \gdtestsummaryview{}.}
-\end{description}
-
-\item Click \bxcaption{OK} to start the report generation.
-\item Once the report is ready, it will be shown in the BIRT viewer.
-\item You can click through the report's pages in the viewer and also export the report as a PDF.
-\bxwarn{The option \bxname{Auto} when exporting a report leads to the right-hand side of the report being cut off.}
-
-\bxtipp{You can also create your own reports to execute with \app{} \bxpref{OwnBIRT}.}
-\end{itemize}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/ownbirt.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/ownbirt.tex
deleted file mode 100644
index 4ba513a3c..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/ownbirt.tex
+++ /dev/null
@@ -1,34 +0,0 @@
-The \app{} BIRT reports are examples of how you could document your quality over time. You can also create other reports to generate depending on which details you want to see in the reports. To create reports, you will need to use the BIRT designer from Actuate. There is an open source version and a commerical version of the designer.
-
-The following information describes what information from the \app{} \gddb{} can be used to generate BIRT reports. For help using BIRT, please see the BIRT documentation.
-
-There are four \gddb{} tables in \app{} that contain relevant data for test results:
-
-\begin{description}
-\item [testresult\_summary]{This table contains one row per executed \gdsuite{} and corresponds to the \gdtestsummaryview{} in \app{}.}
-\item [testresult]{This table contains further information about each test run (each row in the \bxname{testresult\_summary} table), including all executed nodes. }
-\item [parameter\_details]{This table contains the name, type and value for all parameters (data) in the executed test.}
-\item [parameter\_list]{This table gives a parent-child relation between the executed nodes from the \bxname{testresult} table and the parameters in the \bxname{parameter\_details} table.}
-\end{description}
-
-\subsubsection{Creating a BIRT report}
-Using the BIRT report designer, you can create your own reports which will display specific information from these tables.
-
-In the \app{} installation directory, in:
-
-\bxname{plugins/com.bredexsw.guidancer.reporting.birt.viewer}
-
-there is the directory \bxname{reports}.
-
-In this directory, the templates for the reports available in \app{} are stored. There is also a library which uses the \app{} \gddb{} as a data source and contains data sets (SQL queries) to this \gddb{}. The following information is contained in the library:
-
-\begin{description}
-\item [Datasets:]{there are views to show details from the four tables for reporting in the \gddb{}.}
-\item [Report parameters:]{These are parameters for the \gddb{} queries that can be used to limit the scope of a report.}
-\item [Report items:]{These are examples of pre-defined tables and graphs which can be used in other reports.}
-\item [Master pages:]{These define the layout of the reports}
-\item[Themes:]{The themes contain information about colors, fonts etc. The \app{} themes are in the guidancer.css file.}
-\end{description}
-
-\bxwarn{Be careful when working with the reports and themes that you do not break the existing reports in \app{}!}
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/summary.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/summary.tex
index 4327aafc4..602d71900 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/summary.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/summary.tex
@@ -1,6 +1,6 @@
\app{} stores a test result summary and full details about the whole test for each test run. Individual \gdsuites{} within a \gdjob{} are counted as one test run each.
-You can see the test result summaries in the \app{} reporting perspective, in the \gdtestsummaryview{}.
+You can see the test result summaries in the \reportpersp{}, in the \gdtestsummaryview{}.
\subsubsection{Re-opening the test result view for a test run}
\label{TasksReopenTestResult}
@@ -27,6 +27,10 @@ In the context-menu on the column headers in the \gdtestsummaryview{}, you can s
At the top of the \gdtestsummaryview{} there is a filter. Choose which column you want to filter, and enter the value you want to filter by (use \bxshell{*} as a wildcard).
+\subsubsection{Changing the amount of result summaries shown in the \gdtestsummaryview{}}
+\gdhelpid{testResultSummaryViewContextId}{Test Result Summary View}
+
+In the test result preferences \bxpref{testresprefs} you can alter the amount of days that a test result summary is shown. The top of the \gdtestsummaryview{} shows the amount of days that test result summaries are being shown for. Any unshown summaries are not deleted and can be shown by increasing the amount of days.
\subsubsection{Refreshing the \gdtestsummaryview{}}
\gdhelpid{testResultSummaryViewContextId}{Test Result Summary View}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/xmlreport.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/xmlreport.tex
index 3c789c509..f983bd1fa 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/xmlreport.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/xmlreport.tex
@@ -35,14 +35,14 @@ You can create XML and HTML reports for your tests in one of two ways:
\end{itemize}
\end{enumerate}
-\begin{figure}
-\includegraphics{Tasks/Testexecution/PS/htmlpart1}
-\caption{HTML Report Part 1}
-\label{htmlreport1}
-\end{figure}
-\begin{figure}
-\includegraphics{Tasks/Testexecution/PS/htmlpart2}
-\caption{HTML Report Part 2}
-\label{htmlreport2}
-\end{figure}
+%% \begin{figure}
+%% \includegraphics{Tasks/Testexecution/PS/htmlpart1}
+%% \caption{HTML Report Part 1}
+%% \label{htmlreport1}
+%% \end{figure}
+%% \begin{figure}
+%% \includegraphics{Tasks/Testexecution/PS/htmlpart2}
+%% \caption{HTML Report Part 2}
+%% \label{htmlreport2}
+%% \end{figure}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/editing.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/editing.tex
index 980d24b27..9fbc5aeed 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/editing.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/editing.tex
@@ -24,8 +24,8 @@
\begin{itemize}
\item edit the \gdstep{} name
\item add a comment
-\item edit the component, component name and action for the \gdstep{}
-\item edit the parameter values for the \gdstep{}
+\item edit the component, component name and action for the \gdstep{}
+\item edit the parameter values for the \gdstep{} \bxpref{WorkingWithData}
\end{itemize}
\item You can also move the \gdstep{} within the \gdcase{} using drag-and-drop.
\item To delete the \gdstep{}, select:\\
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/specify.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/specify.tex
index b1a697b93..cbe028f01 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/specify.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Teststeps/specify.tex
@@ -54,7 +54,7 @@ purposes, but should be easily identifiable at a later point.
If any of the names are grayed out, this means they have been used for other component types and cannot be used for the currently selected component type.
-You can change, or \bxname{reassign} component names later when you reuse this \gdcase{}. Doing this means that you can execute the same actions on different components in the interface. The section on the \gdcompnamesview{} \bxpref{reass} contains information on reassigning component names.
+You can change, or \bxname{reassign} component names later when you reuse this \gdcase{}. Doing this means that you can execute the same actions on different components in the interface. The section on the \gdcompnamesview{} \bxpref{TasksReassignCompName} contains information on reassigning component names.
\textbf{Action}
@@ -72,13 +72,4 @@ You can see and edit the details of any selected \gdstep{} in the \gdpropview{}.
The next step is to add parameter values (data) for \gdsteps{} in the \gdpropview{} \bxpref{WorkingWithData}.
\end{enumerate}
-%% \textbf{Concrete and abstract components in \gdsteps{}}
-%% \label{teststepcomponent}
-%% \begin{description}
-%% \item[Concrete components]{ are components like \bxname{Combo Box} or \bxname{Text Field/Text Area/...} They refer to one single component or a few closely related components. Choosing a concrete component for a \gdstep{} restricts this \gdstep{} to this component. This isn't a problem if you are sure which component you will be testing.}
-%% \item[Abstract components]{ are components like \bxname{Graphics Component} and \bxname{Button Component}. They are families of components, which all share similar features, and therefore similar action choices. Choosing an abstract component means that you have a larger choice of which real component to test with this \gdstep{}. This is useful if you are at an early stage of development and are not exactly sure which component you will need to test. Choosing abstract components improves the reusability of \gdcases{} because it makes the \gdcase{} more general and flexible. It also makes the test easier to maintain because it increases the chance of being able to simply remap a changed component in the \gdaut{}. }
-%% \end{description}
-
-%% If you have specified a specific toolkit or the \bxname{concrete} toolkit in the \gdaut{} configuration, you will be able to choose between abstract and concrete components. If you specified the \bxname{abstract} toolkit in the \gdaut{} configuration, you can only use abstract components.
-
-
+
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/CONTENT.tex
index bae1ae92c..3c8575199 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/CONTENT.tex
@@ -14,7 +14,7 @@
\label{TSeditor}
\input{Tasks/Testsuite/TSeditorUse}
-\subsection{Configuring \gdsuites{}}
+\subsection{Configuring \gdsuites{} in the \gdpropview{}}
\gdhelpid{guidancerPropertiesViewContextId}{Properties View}
\gdhelpid{testSuiteEditorContextId}{Test Suite Editor}
\gdhelpid{testExecViewContextId}{Test Suite Browser}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/TSeditorUse.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/TSeditorUse.tex
index 0ecf0b748..9e86c012c 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/TSeditorUse.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/TSeditorUse.tex
@@ -33,6 +33,7 @@ from the context-sensitive menu in the \gdtestsuitebrowser{}.
\item Configure the \gdsuite{} in the \gdpropview{} \bxpref{confsuite}.
\item Rename the \gdsuite{} \bxpref{TasksBrowserRename}.
\item Delete \gdcases{} from it \bxpref{TasksEditorDelete}.
+\item Add the \gdsuite{} to a \gdjob{} to be executed along with other \gdsuites{} \bxpref{WorkingWithJobs}.
\end{itemize}
\bxtipp{You can filter in the \gdtestsuitebrowser{} using the field at the top. Use star \bxshell{*} as a wild card.}
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/edit.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/edit.tex
index 1cf031e05..ebc720c7a 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/edit.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testsuite/edit.tex
@@ -1,4 +1,3 @@
-\subsubsection{Configuring \gdsuites{} in the \gdpropview{}}
\index{Test Suite!Configuration}
\index{Configuration!Test Suite}
\index{Event Handler!Error Types}
@@ -31,7 +30,7 @@ To configure a \gdsuite{}, you must first create one \bxpref{TSeditor}.
\item Add a comment to the \gdsuite{} \bxpref{TasksEditorAddComment}.
\item Enter a value in the \bxname{step delay} field.
-\bxtipp{The step delay is the time \app{} leaves between each \gdstep{} during test execution. The default is 0 milliseconds. }
+\bxtipp{The step delay is the time \app{} leaves between each \gdstep{} during test execution. The default is 0 milliseconds. You can also increase the speed of test execution by altering your system settings for double click speed \bxpref{TasksExecSpeed}.}
\item Select the \gdaut{} for this \gdsuite{}. To be able to select an \gdaut{} (and object map, and execute your test) you must have added at least one \gdaut{} to the \gdproject{} \bxpref{Defineaut}.
@@ -43,7 +42,8 @@ To configure a \gdsuite{}, you must first create one \bxpref{TSeditor}.
\gdehandlers{} are \gdcases{} used to deal with errors during test execution. When an error occurs, the current \gdcase{} is searched for an \gdehandler{} for that error type. If none is found, the parent \gdcase{} is searched, and so on. If no \gdehandler{} for the test is found, then a default \gdehandler{} (specified in the \gdsuite{} properties)is activated.
-See the sections on \gdehandlers{} for information on the event types \bxpref{eventtype} and reentry types \bxpref{reentrytype}.
+As a general rule, you should avoid default \gdehandlers{} being executed.
+See the sections on \gdehandlers{} for information on the event types \bxpref{eventtype}, reentry types \bxpref{reentrytype} and creating your own \gdehandlers{}.
\item Save the changes in the \gdtestsuiteeditor{}.
\end{enumerate}
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/CONTENT.tex
index 2144fed20..e1d515156 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/CONTENT.tex
@@ -47,12 +47,8 @@
\label{troublelocked}
\input{Tasks/Troubleshooting/other}
-\subsection{Sending support emails}
-\gdhelpid{problemViewContextId}{Problem View}
-\gdhelpid{supportRequestDialogContextId}{Support Request Email}
-\input{Tasks/Troubleshooting/mail}
+%% \subsection{Sending support emails}
+%% \gdhelpid{problemViewContextId}{Problem View}
+%% \gdhelpid{supportRequestDialogContextId}{Support Request Email}
+%% \input{Tasks/Troubleshooting/mail}
-\subsection{Activating logging}
-\gdhelpid{problemViewContextId}{Problem View}
-\label{TasksActivateLogging}
-\input{Tasks/Troubleshooting/logging}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/aut.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/aut.tex
index cc2f81f78..54123ea83 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/aut.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/aut.tex
@@ -25,7 +25,7 @@
% \bxwarn{} to describe a warning
\index{Errors!AUT}
\index{AUT!Errors}
-\textbf{If the \gdaut{} button is disabled}\\
+\textbf{If the start \gdaut{} button is disabled}\\
If you cannot start a particular \gdaut{}, this could be because:
\begin{itemize}
@@ -46,8 +46,8 @@ class:]{Check that you have entered a JAR which contains a main class.}
\end{description}
-\textbf{If the \gdaut{} does not appear in the \app{}unautview{}}\\
-If the \gdaut{} does not appear in the \app{}unautview{} and you are testing an RCP application, make sure that the RCP-Accessor has been installed \bxpref{rcpaut}.
+\textbf{If the \gdaut{} does not appear in the \gdrunautview{}}\\
+If the \gdaut{} does not appear in the \gdrunautview{} and you are testing an RCP application, make sure that the RCP Remote Control plugin has been installed \bxpref{rcpaut}.
Otherwise, check that the toolkit you specified in the \gdaut{} configuration \bxpref{configuringaut} is the right toolkit for this \gdaut{}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/failedsuite.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/failedsuite.tex
index b11d70c2f..f963b2262 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/failedsuite.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/failedsuite.tex
@@ -17,18 +17,19 @@
%% \end{document}
\index{Test Suite!Failed}
-If your test fails, you can find exact details about the problem by looking at the \gdtestresultview{} \bxpref{testresultview}.
+If your test fails, you can find exact details about the problem by looking at the \gdtestresultview{} \bxpref{testresultview}. A screenshot of the \gdaut{} is automatically taken when an error occurs and can be seen in the \gdimgview{}.
For other problems with test execution, check:
\begin{itemize}
-\item That the \gdaut{} is in focus and is visible. You can automatically activate the \gdaut{} in the \gdaut{} properties \bxpref{configuringaut}. You can also set your preferences to minimize \app{} when test execution begins \bxpref{gdprefs}.
+\item That the \gdaut{} is in focus and is visible. You can automatically activate the \gdaut{} in the \gdaut{} properties \bxpref{configuringaut} or you can use a \gdcase{} to activate the \gdaut{}. You can also set your preferences to minimize \app{} when test execution begins \bxpref{gdprefs}.
\item That the \gdaut{} is ready when the test begins. To ensure this, you can insert a \gdcase{} at the beginning of each test which waits for the window or for the first component you want to test.
\bxtipp{Waiting for a window to appear is generally a good idea whenever a new window or dialog is opened during the test. Waiting for the window or the component you want to test will make sure that your tests run even under different timing conditions. }
\item Make sure that the \gdcases{} and \gdsteps{} are in the right order.
\item Ensure that the data you have entered is correct.
\item Check your object mapping preferences \bxpref{objectprefs}. We recommend that you set them to \bxcaption{standard}.
-\item If the \gdaut{} is an RCP application, make sure that the keyboard layout is correct \bxpref{configuringaut}. Otherwise, make sure you have the current version of the RCP-Accessor (start your application with -clean to be sure).
+\item If the \gdaut{} is an RCP application, make sure that the keyboard layout is correct \bxpref{configuringaut}. Otherwise, make sure you have the current version of the RCP Remote Control plugin (start your application with -clean to be sure).
\item Check that the \gdsteps{} preceding the failed \gdstep{} were successful by looking at the state of the application.
\end{itemize}
+\bxtipp{To help you analyze the reasons for \gdsuite{} failure, you can use the \bxname{pause on error} option \bxpref{TasksPauseOnError}.}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/intro.tex
index a8fb452b9..06b178328 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/intro.tex
@@ -29,11 +29,11 @@
\subsection{General help}
Always check in the \gdprobview{} first for any help with your tests. The messages there should help you with most of the problems. \app{} also highlights problems in the browsers and views with red crosses. Hover the mouse over the item to see a tool tip with more information.
-In some text fields in \app{} you can only enter certain characters. A red background in a text field means that you have entered something incorrect in that field. A yellow background means that the information entered is incomplete.
+In some text fields you can only enter certain characters. A red background in a text field means that you have entered something incorrect in that field. A yellow background means that the information entered is incomplete.
-Looking in the log files may help to resolve some problems. If file-based logging is enabled \bxpref{TasksActivateLogging}, logs for the \jbclient{} and \gdagent{} can be found via:\\
+Looking in the log files may help to resolve some problems. Logs for the \jbclient{} and \gdagent{} can be found via:\\
\bxmenu{Help}{Show Client/\gdagent Log}{}
-\bxtipp{The \jbclient{} can only access an \gdagent{} log file if it is currently connected to a \gdagent{}.}
+\bxtipp{The \ite{} can only access an \gdagent{} log file if it is currently connected to a \gdagent{}.}
This section contains information on some of the more common problems:
\begin{itemize}
@@ -47,7 +47,7 @@ This section contains information on some of the more common problems:
\end{itemize}
-For other problems, look in the relevant section of the user manual or the reference manual. There are FAQs on the \app{} website, and our support team is happy to help with any outstanding questions.
+For other problems, look in the relevant section of the user manual or the reference manual. There are also FAQs on the \app{} website.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/logging.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/logging.tex
deleted file mode 100644
index c6adf3c2d..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/logging.tex
+++ /dev/null
@@ -1,30 +0,0 @@
-% BREDEX LaTeX Template
-% \documentclass is either ``bxreport'' or ``bxarticle''
-% option is bxpaper
-%% \documentclass{bxarticle}
-%% % ----------------------------------------------------------------------
-%% \begin{document}
-%% \title{}
-%% \author{}
-%% % \author*{Hauptautor}{Liste der Nebenautoren}
-%% \maketitle
-%% % ----------------------------------------------------------------------
-%% \bxversion{0.1}
-%% %\bxdocinfo{STATUS}{freigegeben durch}{freigegeben am}{Verteilerliste}
-%% \bxdocinfo{DRAFT}{}{}{}
-%% % ----------------------------------------------------------------------
-
-%% \end{document}
-\index{Logging}
-\index{Client!Logging}
-\index{AUT Agent!Logging}
-To enable logging:
-\begin{enumerate}
-\item Open the configuration tool from the start menu or command line.
-\item When prompted, browse to the installation directory for the \app{} installation you want to configure (if you only have one installation, accept the default).
-\item In the tabs for client logging and \gdagent{} logging, choose \bxname{log file} as the logging method, and enter a path to a file where you have write access.
-\item Close the configuration tool by clicking \bxcaption{OK}.
-\item Via the help menu in \app{} (after a restart), you can now show the logs for the client and the \gdagent{}.
-\end{enumerate}
-
-
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/mail.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/mail.tex
index e04e63937..3cc17cb27 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/mail.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/mail.tex
@@ -18,6 +18,5 @@ You can send support emails to \app{} support from within the \app{} client. The
\bxtipp{Any \gdprojects{} you add are first exported to a temporary directory on your computer.}
\item Click \bxcaption{OK}.
\item The prepared email will be opened with the selected attachments already added.
-\item Enter a text with a short description of the problem, and send us the email.
-\item We will be in touch with an answer as soon as possible.
+
\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/servererrors.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/servererrors.tex
index 669a83aa2..8e96836ea 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/servererrors.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Troubleshooting/servererrors.tex
@@ -27,7 +27,7 @@
\index{Errors!AUT Agent}
Check:
\begin{itemize}
-\item That you have used the right port number and that it is not being used by any other program. If the \gdagent logging is switched on, you can see the currently used port number in the log file.
+\item That you have used the right port number and that it is not being used by any other program.
\item Whether the computer on which the \gdagent is installed is switched on.
\item That there are no network problems, and that all necessary hardware is connected.
\end{itemize}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/intro.tex
index fa3b2501d..648b14e90 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/intro.tex
@@ -39,25 +39,25 @@ You can change the way your user interface looks by moving areas, changing the c
To reset the default layout at any time, select:\\
\bxmenu{Window}{Reset Perspective}{}.
-\subsection{Color coding}
-Because \app{} contains user interface elements whose contents change depending on what is selected, we use a color coding system to distinguish between areas used for specification and execution.
-
-The areas used for specification have brown borders by default. These are:
-\begin{itemize}
-\item The \gdtestcasebrowser{}
-\item The \gdtestcaseeditor{}
-\item The \gdpropview{}, \gdcompnamesview{} and \gddatasetsview{} when they are showing details about an item selected in one of the two areas above.
-\end{itemize}
-
-The areas used for execution have blue borders by default. These are:
-\begin{itemize}
-\item The \gdtestsuitebrowser{}
-\item The \gdtestsuiteeditor{}
-\item The \gdtestresultview{}
-\item The \gdpropview{}, \gdcompnamesview{} and \gddatasetsview{} when they are showing details about an item selected in one of the three areas above.
-\end{itemize}
-
-You can change the colors or switch the color coding off in the \bxcaption{appearance} preferences.
+%% \subsection{Color coding}
+%% Because \app{} contains user interface elements whose contents change depending on what is selected, we use a color coding system to distinguish between areas used for specification and execution.
+
+%% The areas used for specification have brown borders by default. These are:
+%% \begin{itemize}
+%% \item The \gdtestcasebrowser{}
+%% \item The \gdtestcaseeditor{}
+%% \item The \gdpropview{}, \gdcompnamesview{} and \gddatasetsview{} when they are showing details about an item selected in one of the two areas above.
+%% \end{itemize}
+
+%% The areas used for execution have blue borders by default. These are:
+%% \begin{itemize}
+%% \item The \gdtestsuitebrowser{}
+%% \item The \gdtestsuiteeditor{}
+%% \item The \gdtestresultview{}
+%% \item The \gdpropview{}, \gdcompnamesview{} and \gddatasetsview{} when they are showing details about an item selected in one of the three areas above.
+%% \end{itemize}
+
+%% You can change the colors or switch the color coding off in the \bxcaption{appearance} preferences.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/perspectives.tex b/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/perspectives.tex
index b547ae936..deeb7aa84 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/perspectives.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/perspectives.tex
@@ -57,7 +57,7 @@ The specification perspective (\bxfigref{clientwindow}) provides browsers, edito
\item The \gdcompnamesview{}
\item The \gdprobview{}
\item The search result view (behind the \gdprobview{})
-\item The \app{}unautview{}
+\item The \gdrunautview{}
\end{itemize}
\begin{figure}
@@ -154,11 +154,11 @@ In the workspace perspective (\bxfigref{workspaceperspective}), you can view the
\index{Reporting!Perspective}
\index{Views!Test Result Summary}
\index{Test Result Summary View}
-In the reporting perspective, the only view is the \gdtestsummaryview{}. You can see an overview of all tests that have run in this \gddb{} and can generate \app{} BIRT reports from the perspective.
+In the reporting perspective, the only view is the \gdtestsummaryview{}. You can see an overview of all tests that have run in this \gddb{}.
\begin{figure}
\includegraphics[width=12.5cm]{Userinterface/Editors/PS/reportingperspective}
\caption{\app{} Reporting Perspective}
\label{reportingperspective}
\end{figure}
-\clearpage \ No newline at end of file
+\clearpage
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/views.tex b/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/views.tex
index faa31443b..d118f1cda 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/views.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Userinterface/Editors/views.tex
@@ -51,7 +51,7 @@
\item Console
\item \gdinspector{}
\item \gdtestsummaryview{}
-\item \app{}unautview{}
+\item \gdrunautview{}
\item \gdimgview{}
\end{itemize}
@@ -197,10 +197,10 @@ The console is underneath the \gdmodeleditor{} in the modeling perspective and b
The \gdinspector{} can be used to help you test RCP \gdauts{} which use the GEF framework. When the inspector is activated, figures can be clicked in the GEF canvas, and their textpath (used to identify them in the test) is shown. The \gdinspector{} is shown by default in the bottom right-hand corner of the specification perspective.
\subsection{The \gdtestsummaryview{}}
-The \gdtestsummaryview{} offers an overview of all tests that have run in this \gddb{}. It can be filtered and sorted, and from this view you can generate \app{} BIRT reports. The \gdtestsummaryview{} is displayed in the \app{} reporting perspective.
+The \gdtestsummaryview{} offers an overview of all tests that have run in this \gddb{}. It can be filtered and sorted. The \gdtestsummaryview{} is displayed in the \reportpersp{}.
-\subsection{The \app{}unautview{}}
-The \app{}unautview{} is above the \gdtestsuitebrowser{} in the specification perspective. It shows an overview of all running \gdauts{} and can be used to stop \gdauts{} and to start \gdsuites{}.
+\subsection{The \gdrunautview{}}
+The \gdrunautview{} is above the \gdtestsuitebrowser{} in the specification perspective. It shows an overview of all running \gdauts{} and can be used to stop \gdauts{} and to start \gdsuites{}.
\subsection{The \gdimgview{}}
The \gdimgview{} is used to see automatically generated screenshots of errors that have occurred in tests.

Back to the top