Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'org.eclipse.jubula.documentation/manual/en/tex/Samples/Meters/test.tex')
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Samples/Meters/test.tex4
1 files changed, 0 insertions, 4 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Samples/Meters/test.tex b/org.eclipse.jubula.documentation/manual/en/tex/Samples/Meters/test.tex
index 0db7d2a40..6900f1520 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Samples/Meters/test.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Samples/Meters/test.tex
@@ -9,9 +9,5 @@ The test for the meters tool contains three use cases.
In the \bxname{bound\_modules\_samples} \gdproject{}, you can see the building blocks that these use cases are made up of in the \bxname{AUT bound modules} category.
-\subsubsection{Excel files}
-The meters tests use Excel files to provide most of the data they need. In the Excel files, you can see that the test can run in German and English. Change the working language before starting the \gdaut{} to start the \gdaut{} and run the test in a different language.
-
-
\subsubsection{Concatenated parameters}
The meters application has a fairly complex tree structure in terms of the data in it. Look in the \gdcase{} \bxname{mtr\_tre\_selectNode} in the \bxname{bound\_modules\_samples} \gdproject{} to see how the treepath has been concatenated out of the concrete value \bxname{Building} and then two further parameters for the location of the meter and the meter number. This makes entering the test data easier.

Back to the top