Skip to main content
diff options
authorAlexandra Schladebeck2013-05-15 13:40:25 +0000
committerAlexandra Schladebeck2013-05-15 13:40:25 +0000
commit80761318605df520084b2327bd744cfba7e43b23 (patch)
parenta920dbf230c01c8d67dc81942a419be022245ae2 (diff)
Non sprint task: Removed docu for embedded Chronon
4 files changed, 8 insertions, 39 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/CONTENT.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/CONTENT.tex
index 6426ccac9..fc495259f 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/CONTENT.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/CONTENT.tex
@@ -1,8 +1,5 @@
-\subsection{Using Chronon in \app{}}
\subsection{Using Chronon when testing your \gdaut{}}
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/embedded.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/embedded.tex
deleted file mode 100644
index 83fd91bed..000000000
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/embedded.tex
+++ /dev/null
@@ -1,35 +0,0 @@
-\index{Chronon!Embedded support}
-The embedded support for Chronon in \app{} lets you record debug information while you are working with \app{}. Should an error occur, the Chronon report can be added to any bug reports or support conversations to help our team analyze the problem.
-\subsubsection{Turning on the recording}
-\item You can activate the Chronon recording in \app{} by selecting:\\
-\bxmenu{Help}{Start Chronon Recorder}{}\\
-\bxwarn{Linux users: you must first comment Chronon in for the \ite{} in the .ini file by removing the hash signs from the two lines in the .ini file, and then restart \app{}. If you are starting \app{} from the command line with Chronon on Linux, please ensure that your current directory is the \app{} directory, otherwise \app{} will not start.}
-\item The Progress View will open and you will see the status of the recording. The progress bar continues to run once the recorder has started. The status changes from \bxname{starting} to \bxname{running}. When the recorder is running, you will be able to see the job running in the Progress View and also in the status bar. Do not stop the job -- this will stop the recording.
-\item Once the recorder is running, your actions in \app{} are written to the recording file.
-\bxtipp{Bear in mind that any data contained within \app{} may be visible by our development team when analysing any Chronon files}.
-\bxtipp{We do not recommend running the Chronon recorder constantly, as the collection of additional information can lead to detractions in performance in \app{}. Instead, we would recommend turning Chronon on when you specifically want to reproduce a problem, and turning it off afterwards. Additionally, you should ensure that you have increased the heap space to avoid running into memory problems.}
-\subsubsection{Turning off the recording}
-You can deactivate the Chronon recording by opening the Progress View and clicking the \bxcaption{Stop} button.
-Restarting or closing \app{} will also stop the recording.
-\subsubsection{Accessing the Chronon report}
-The Chronon reports are saved by default to:\\
-You can alter this location, as well as setting exclude and include patterns for the Chronon recording in the preferences \bxpref{TasksPrefsChronon}.
-When working with Chronon in \app{} itself, a new folder is created for each recording session (one session = starting - recording - stopping). The relevant folder for a bug report can be zipped and attached to help our analysis.
-\subsubsection{Increasing the heap space to improve working with Chronon}
-Having the Chronon recorder running is very memory-intensive. You will almost certainly have to increase the heap space allocated to \app{}. You can do this in the .ini file for \app{}.
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/intro.tex
index 9de6499ce..d750ff076 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Tasks/Chronon/intro.tex
@@ -1,4 +1,5 @@
-\app{} supports Chronon (3.0) as a monitoring agent to record information about the use of \app{} itself as well the behavior of your \gdaut{} during a test.
+\app{} supports Chronon (3.0) as a monitoring agent to record information about the behavior of your \gdaut{} during a test.
The information gathered by Chronon can be used to help analyze any errors found in the program.
\bxwarn{\jb{} users: the Chronon plugins are only available in the standalone version.}
diff --git a/org.eclipse.jubula.documentation/releasenotes/en/tex/71/jubulaissues.tex b/org.eclipse.jubula.documentation/releasenotes/en/tex/71/jubulaissues.tex
index 4142e8c66..7728e9ab3 100644
--- a/org.eclipse.jubula.documentation/releasenotes/en/tex/71/jubulaissues.tex
+++ b/org.eclipse.jubula.documentation/releasenotes/en/tex/71/jubulaissues.tex
@@ -9,3 +9,9 @@
\item The multi-window mode for HTML \gdauts{} is considerably slower on IE than on Firefox.
\item This is a known issue that is registered at Selenium.
+\textbf{Embedded Chronon support removed}
+\item The embedded Chronon support for the standalone versions has been removed.
+\item You can still configure your \gdaut{} to run with Chronon.

Back to the top