Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'org.eclipse.jubula.documentation/manual/en/tex/Tasks')
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/intro.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/configfile.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/embedded.tex8
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Commandline/parameters.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/CONTENT.tex4
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/intro.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/parameters.tex8
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/starting.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex1
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testresults/summary.tex1
10 files changed, 26 insertions, 16 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/intro.tex
index d0ed5d110..9e5825fca 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/intro.tex
@@ -1 +1,5 @@
+Select an item in a browser to see read-only details in the \gdpropview{}, \gddatasetsview{} and \gdcompnamesview{} for this item.
+
You can rename items from the \gdtestcasebrowser{}, \gdtestsuitebrowser{} or \gdcompnamebrowser{}.
+
+You can open editors for items in certain browsers. See the later section \bxpref{WorkingWithEditors} for more details.
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 763044171..320af2637 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
@@ -38,8 +38,8 @@ For example:
<autconfig>local configuration</autconfig>
OR
<autid>Adder</autid>
- <dbscheme>Embedded</dbscheme>
- <dbuser></dbuser>
+ <dbscheme>embedded</dbscheme>
+ <dbuser>sa</dbuser>
<dbpw></dbpw>
<server>localhost</server>
<port>60000</port>
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 cc7a81ff2..13a7668d2 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
@@ -2,9 +2,9 @@
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]{<empty>}
-\item[-dbpw]{<empty>}
+\item[-dbscheme]{embedded}
+\item[-dbuser]{sa}
+\item[-dbpw]{<empty> (\bxshell{''''})}
\end{description}
-If you have changed the name of the default \gddb{} scheme in the configuration tool, you should alter the parameter for the \bxname{-dbscheme} accordingly.
+If you have changed the name of the default \gddb{} scheme in the \gddb{} preferences \bxpref{TasksPrefsDB}, you should alter the parameter for the \bxname{-dbscheme} accordingly.
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 ec4b82b0d..78c112ead 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
@@ -41,10 +41,12 @@
\gdaut{} configuration name
& \bxshell{-autconfig <configuration name>}\\
&e.g. \emph{-autconfig ''localconfiguration''}\\
+ &Use when starting an \gdaut{} via a configuration.\\
\hline
\gdaut{} ID
& \bxshell{-autid <ID>}\\
&e.g. \emph{-autid ''SimpleAdder1''}\\
+ &Use when \gdaut{} was started via \bxname{autrun}.\\
\hline
Configuration file
& \bxshell{-c <path to configuration file>}\\
@@ -77,10 +79,12 @@
Test Suite
& \bxshell{-testsuite <testsuite name>}\\
&e.g. \emph{-testsuite ''suite1''}\\
+ &Use to start a \gdsuite{}\\
\hline
Test Job
& \bxshell{-testjob <testjob name>}\\
&e.g. \emph{-testjob ''job1''}\\
+ &Use to start a \gdjob{}\\
\hline
Workspace
& \bxshell{-data <path to workspace>}\\
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/CONTENT.tex
index 100820cb3..49e90721d 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/CONTENT.tex
@@ -1,7 +1,7 @@
\input{Tasks/DBTool/intro}
-\subsection{Starting the GUIdancerDBTool}
+\subsection{Starting the dbtool}
\input{Tasks/DBTool/starting}
-\subsection{Parameters for the GUIdancerDBTool}
+\subsection{Parameters for the dbtool}
\input{Tasks/DBTool/parameters}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/intro.tex
index f8f0c70f5..498082c06 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/intro.tex
@@ -1,3 +1,3 @@
-You can use the \app{} \gddb{} tool (GUIdancerDBTool) to import, export and delete \gdprojects{} from the \gddb{} in \app{} without using the \app{} client.
+You can use the dbtool to import, export and delete \gdprojects{} from the \gddb{} in without using the \ite{}.
This is particularly useful for automated build and test processes, where you may want to automatically export and import \gdprojects{} out of and into version control to run your tests.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/parameters.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/parameters.tex
index 1bb2002cb..14b44d915 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/parameters.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/parameters.tex
@@ -1,7 +1,7 @@
-\index{DB Tool}
+\index{dbtool}
\begin{enumerate}
-\item Once you have browsed to the \app{} installation directory and entered \bxshell{GUIdancerDBTool}, you can enter the parameters for the \gddb{} actions.
-\item The DBTool uses the parameters described in the table \bxfigref{dbtoolparams}:
+\item Once you have browsed to the \app{} installation directory and entered \bxshell{dbtool}, you can enter the parameters for the \gddb{} actions.
+\item The dbtool uses the parameters described in the table \bxfigref{dbtoolparams}:
\begin{table}[h]
@@ -63,7 +63,7 @@
&If no URL is given, the default will be used.\\
\hline
\end{tabular}
- \caption{Parameters for the DBTool}
+ \caption{Parameters for the dbtool}
\end{table}
\item You can use the parameter \bxshell{-keepsummary} to specify that the test result summaries should not be deleted when the \gdproject{} or \gdprojects{} are deleted. This is useful for continuous integration processes, where the test results over time should be kept, but the \gdprojects{} are reimported into the \gddb{} (for example from the version control system) each night. If you do not enter this parameter, the summaries will be deleted with the \gdprojects{}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/starting.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/starting.tex
index e3aae4e8b..7e563f72e 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/starting.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/DBTool/starting.tex
@@ -1,10 +1,10 @@
-\index{DB Tool}
+\index{dbtool}
\begin{enumerate}
\item In a command line interface, locate the \app{} installation directory and open the \app{} directory within it.
-\item Enter \bxshell{GUIdancerDBTool.exe}.
+\item Enter \bxshell{dbtool.exe}.
-This will run the executable \emph{GUIdancerDBTool.exe}.
+This will run the executable \emph{dbtool.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}
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 02dbb961a..cf0fcd613 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/SECTIONS.tex
@@ -114,6 +114,7 @@ For more details about individual tasks, read the \bxref{Concepts}
\clearpage
\section{Test execution}
+\label{TestExec}
\input{Tasks/Testexecution/CONTENT}
\clearpage
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 602d71900..e18702402 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
@@ -3,6 +3,7 @@
You can see the test result summaries in the \reportpersp{}, in the \gdtestsummaryview{}.
\subsubsection{Re-opening the test result view for a test run}
+\gdhelpid{testResultSummaryViewContextId}{Test Result Summary View}
\label{TasksReopenTestResult}
\begin{enumerate}
\item If the full details for a test run are still available (the column \bxname{Details} shows \bxname{true}), you can re-open the full test result by double-clicking on the entry in the \gdtestsummaryview{} or by clicking the button to open the report in the top right-hand corner of the view.

Back to the top