Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'org.eclipse.jubula.documentation/manual/en/tex/Concepts/Strategy/intro.tex')
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Concepts/Strategy/intro.tex9
1 files changed, 2 insertions, 7 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Concepts/Strategy/intro.tex b/org.eclipse.jubula.documentation/manual/en/tex/Concepts/Strategy/intro.tex
index 63755dd3d..0bf44acf2 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Concepts/Strategy/intro.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Concepts/Strategy/intro.tex
@@ -7,11 +7,6 @@
% User documentation
% copyright by BREDEX GmbH 2004
% --------------------------------------------------------
-\index{Top-Down Specification}
-\index{Bottom-Up Specification}
-\index{Specification!Approaches!Top-Down}
-\index{Specification!Approaches!Bottom-Up}
-\app{} supports both bottom-up and top-down testing. You can even use both methods in the same \gdproject{}, and often, you can easily change between the two.
-The following sections explain a little about each approach, and its advantages and disadvantages.
-The best method to choose will depend on the size and type of the \gdproject{}, the stage of testing, the \gdaut{} and your personal preferences. \ No newline at end of file
+\app{} supports modular testing. You can either create modules in advance and combine them to make larger \gdcases{}, or you can create modules from existing \gdcases{} when you realize you need them.
+

Back to the top