Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/BestPractices/Structure/tcb.tex2
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/CONTENT.tex6
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/categories.tex34
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/CONTENT.tex16
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/create.tex9
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/existing.tex13
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/intro.tex1
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Objectmapping/editor.tex1
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/Testdata/central.tex1
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Tasks/content.tex11
-rw-r--r--org.eclipse.jubula.documentation/releasenotes/en/tex/60/jubulafeatures.tex22
11 files changed, 59 insertions, 57 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/BestPractices/Structure/tcb.tex b/org.eclipse.jubula.documentation/manual/en/tex/BestPractices/Structure/tcb.tex
index 5bb5ba4cb..0c2b32f1c 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/BestPractices/Structure/tcb.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/BestPractices/Structure/tcb.tex
@@ -1,4 +1,4 @@
-We recommend using categories \bxpref{TasksBrowserCats} to structure the \gdtestcasebrowser{}. This makes your keywords easier to find when you are creating tests.
+We recommend using categories \bxpref{WorkingWithCategories} to structure the \gdtestcasebrowser{}. This makes your keywords easier to find when you are creating tests.
We recommend using two main categories to organize the \gdtestcasebrowser{}: executable tests and modules.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/CONTENT.tex
index 0200dc517..33553f7a0 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/CONTENT.tex
@@ -8,12 +8,6 @@
\label{TasksBrowserRename}
\input{Tasks/Browsers/rename}
-\subsection{Working with categories in browsers}
-\gdhelpid{testSpecificationViewContextId}{Test Case Browser}
-\gdhelpid{testExecViewContextId}{Test Suite Browser}
-\gdhelpid{dialogNewCategoryContextId}{New Category Dialog}
-\label{TaskBrowserCats}
-\input{Tasks/Browsers/categories}
\subsection{Deleting items from browsers}
\gdhelpid{testSpecificationViewContextId}{Test Case Browser}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/categories.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/categories.tex
deleted file mode 100644
index 733d874eb..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Browsers/categories.tex
+++ /dev/null
@@ -1,34 +0,0 @@
-\index{Categories!Test Cases}
-\index{Test Case!Categories}
-\index{Categories!Test Suites}
-\index{Test Suite!Categories}
-\index{Categories!Test Jobs}
-\index{Test Job!Categories}
-
-
-Categories let you group \gdcases{}, \gdsuites{} and \gdjobs{} together in the \gdtestcasebrowser{} or \gdtestsuitebrowser{}.
-
-\textbf{Creating a category:}
-\begin{enumerate}
-\item In the \gdtestcasebrowser{} or \gdtestsuitebrowser{}, select:\\
-\bxmenu{New}{Category}{} from the context-sensitive menu.
-\item Name the category when prompted.
-\item In the \gdtestcasebrowser{}, you can add \gdcases{} to this category using drag-and-drop. In the \gdtestsuitebrowser{}, you can add \gdsuites{} and \gdjobs{} to your categories.
-\item You can also nest categories in other categories.
-\item You can do this either by dragging and dropping a category into another category, or by right-clicking in an already present category and choosing the option to create a new category.
-\bxtipp{For best practices on how to use categories in the \gdtestcasebrowser{}, see the section on Best Practices \bxpref{BPCategories}}
-\end{enumerate}
-
-\textbf{Creating \gdcases{} within an already existing category:}
-\begin{enumerate}
-\item To create a \gdcase{} in an already existing category, select the category in which you want to create the \gdcase{} with a single-click in the \gdtestcasebrowser{}.
-\item Create a \gdcase{} via the context-sensitive menu \bxpref{TasksCreateTC}.
-\item You can also simply double-click on the category in which you want to create the \gdcase{}.
-\end{enumerate}
-
-\textbf{Creating \gdsuites{} and \gdjobs{} within an already existing category:}
-\begin{enumerate}
-\item To create a \gdsuite{} or a \gdjob{} in an already existing category, select the category in which you want to create the \gdsuite{} or \gdjob{} with a single-click in the \gdtestsuitebrowser{}.
-\item Create a \gdsuite{} or \gdjob{} via the context-sensitive menu \bxpref{TSeditor}.
-%\item You can also simply double-click on the category in which you want to create the \gdcase{}.
-\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/CONTENT.tex
new file mode 100644
index 000000000..2078c6947
--- /dev/null
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/CONTENT.tex
@@ -0,0 +1,16 @@
+\index{Categories!Test Cases}
+\index{Test Case!Categories}
+\index{Categories!Test Suites}
+\index{Test Suite!Categories}
+\index{Categories!Test Jobs}
+\index{Test Job!Categories}
+
+\input{Tasks/Categories/intro}
+
+\subsection{Creating a category}
+\input{Tasks/Categories/create}
+
+\subsection{Creating \gdcases{}, \gdsuites{} and \gdjobs{} in an existing category}
+\input{Tasks/Categories/existing}
+
+
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/create.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/create.tex
new file mode 100644
index 000000000..b28e6a2a9
--- /dev/null
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/create.tex
@@ -0,0 +1,9 @@
+\begin{enumerate}
+\item In the browser or editor, select:\\
+\bxmenu{New}{Category}{} from the context-sensitive menu.
+\item Name the category when prompted.
+\item Once you have a category, you can add items to it by drag and drop, and also by double-clicking to add new items (only in the browsers).
+\item You can also nest categories in other categories.
+\item You can do this either by dragging and dropping a category into another category, or by right-clicking in an already present category and choosing the option to create a new category.
+\bxtipp{For best practices on how to use categories in the \gdtestcasebrowser{}, see the section on Best Practices \bxpref{BPCategories}}
+\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/existing.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/existing.tex
new file mode 100644
index 000000000..0c026f3dc
--- /dev/null
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/existing.tex
@@ -0,0 +1,13 @@
+\textbf{Creating \gdcases{} within an already existing category:}
+\begin{enumerate}
+\item To create a \gdcase{} in an already existing category, select the category in which you want to create the \gdcase{} with a single-click in the \gdtestcasebrowser{}.
+\item Create a \gdcase{} via the context-sensitive menu \bxpref{TasksCreateTC}.
+\item You can also simply double-click on the category in which you want to create the \gdcase{}.
+\end{enumerate}
+
+\textbf{Creating \gdsuites{} and \gdjobs{} within an already existing category:}
+\begin{enumerate}
+\item To create a \gdsuite{} or a \gdjob{} in an already existing category, select the category in which you want to create the \gdsuite{} or \gdjob{} with a single-click in the \gdtestsuitebrowser{}.
+\item Create a \gdsuite{} or \gdjob{} via the context-sensitive menu \bxpref{TSeditor}.
+\item To create a \gdsuite{}, you can also simply double-click on the category in which you want to create the \gdsuite{}.
+\end{enumerate}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/intro.tex
new file mode 100644
index 000000000..9c3ada569
--- /dev/null
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Categories/intro.tex
@@ -0,0 +1 @@
+Categories let you group items together to be able to keep an overview of your data and find things more easily. You can use categories in the \gdtestcasebrowser{}, in the \gdtestsuitebrowser{}, in the \gddataeditor{} and in the \gdomeditor{} (see the section on object mapping for information on categories in the \gdomeditor{} \bxpref{TasksOMCategories}).
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 ca9f39b44..e9da6ca11 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
@@ -12,6 +12,7 @@
\subsubsection{Working with categories in the \gdomeditor{}}
\gdhelpid{objectMapEditorContextId}{Object Mapping}
\gdhelpid{dialogOMCategoryNewContextId}{New Object Mapping Category Dialog}
+\label{TasksOMCategories}
\input{Tasks/Objectmapping/categories}
\subsubsection{The configuration view in the \gdomeditor{}}
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 d1ca086c1..210103aa0 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
@@ -18,6 +18,7 @@ from the context-sensitive menu or press \bxkey{Insert}.
\item You can rename the data set by pressing\bxkey{F2} or selecting:\\
\bxmenu{Rename}{}{}\\
from the context sensitive menu.
+\item You can categorize your central data sets using the \bxname{Add category} function from the context-sensitive menu \bxpref{WorkingWithCategories}.
\end{enumerate}
\subsubsection{Deleting central test data sets}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/content.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/content.tex
index ddd634ad2..7df6b6a9f 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/content.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/content.tex
@@ -28,14 +28,21 @@ For more details about individual tasks, read the \bxref{Concepts}
\input{Tasks/AUTs/CONTENT}
\clearpage
-\section{Working with browsers}
+\section{Working with browsers: renaming, deleting, using IDs}
\label{WorkingWithBrowsers}
\input{Tasks/Browsers/CONTENT}
-\section{Working with editors}
+\section{Working with editors: opening, adding/deleting/renaming items, commenting, extracting and replacing, reverting changes}
\label{WorkingWithEditors}
\input{Tasks/Editors/CONTENT}
+\section{Working with categories in the browsers and editors}
+\gdhelpid{testSpecificationViewContextId}{Test Case Browser}
+\gdhelpid{testExecViewContextId}{Test Suite Browser}
+\gdhelpid{dialogNewCategoryContextId}{New Category Dialog}
+\label{WorkingWithCategories}
+\input{Tasks/Categories/CONTENT}
+
\clearpage
\section{Working with \gdcases{}}
\gdhelpid{testSpecificationViewContextId}{Test Case Browser}
diff --git a/org.eclipse.jubula.documentation/releasenotes/en/tex/60/jubulafeatures.tex b/org.eclipse.jubula.documentation/releasenotes/en/tex/60/jubulafeatures.tex
index fd9d40c72..fa9b055ca 100644
--- a/org.eclipse.jubula.documentation/releasenotes/en/tex/60/jubulafeatures.tex
+++ b/org.eclipse.jubula.documentation/releasenotes/en/tex/60/jubulafeatures.tex
@@ -7,10 +7,10 @@ without having to set timers or manually check timestamps.
\item You can switch off the decoration in the \app{} client in the \bxname{label decoration} preferences.
\end{itemize}
-\textbf{Categories now supported in the \gdtestsuitebrowser{}}\\
+\textbf{Categories now supported in the \gdtestsuitebrowser{} and \gddataeditor}\\
\begin{itemize}
-\item It is now possible to create categories for \gdsuites{} and \gdjobs{} in the \gdtestsuitebrowser{}.
-\item Existing \gdprojects{} will be shown as having two categories (\bxname{Test Suites} and \bxname{Test Jobs}) as was previously the case. However, you can now rename, delete and rearrange categories in the \gdtestsuitebrowser{}.
+\item It is now possible to create categories for \gdsuites{} and \gdjobs{} in the \gdtestsuitebrowser{}, as well as for central data sets in the \gddataeditor{}.
+\item Existing \gdprojects{} will be shown as having two categories (\bxname{Test Suites} and \bxname{Test Jobs}) in the \gdtestsuitebrowser{} as was previously the case. However, you can now rename, delete and rearrange categories in the \gdtestsuitebrowser{}.
\end{itemize}
\textbf{Parameter values now shown for each node in \gdtestresultview{}}\\
@@ -20,14 +20,8 @@ without having to set timers or manually check timestamps.
\item You can switch off the decoration in the \app{} client in the \bxname{label decoration} preferences.
\end{itemize}
-%% \textbf{Support for adding basic component extensions to a \gdproject{}}\\
-%% \begin{itemize}
-%% \item Alongside the full extension mechanism for adding new supported components and actions, there is now an easier way to add basic support
-%% for as yet unsupported components.
-%% \item In the \gdproject{} properties, there is a new area for \bxname{Component Extensions}. On this page, you can enter the class name
-%% (e.g. \bxname{javax.swing.JSeparator}) for currently unsupported components.
-%% \item The component types you add must be of the type \bxname{JComponent} in Swing and \bxname{Control} in SWT. This mechanism is not currently supported for HTML \gdauts{}.
-%% \item Once you have added the component, you will be able to collect components of this type in the \gdomm{} and you will be able to perform
-%% actions on them that are defined for \bxname{Graphics Component} (i.e. clicking, waiting for them, checking their existence, enablement, focus and properties).
-%% \end{itemize}
-
+\textbf{Completeness check shown as progress window}\\
+\begin{itemize}
+\item After saving in the \ite{}, the completeness check which validates the state of the \gdproject{} (test data, object mapping, missing \gdcases{} etc) is now shown explicitly as a progress window.
+\item This results from performance improvements made to the completeness check.
+\end{itemize}

Back to the top