Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'org.eclipse.jubula.documentation/manual/en/tex/Introduction/Intro/approaches.tex')
-rw-r--r--org.eclipse.jubula.documentation/manual/en/tex/Introduction/Intro/approaches.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/org.eclipse.jubula.documentation/manual/en/tex/Introduction/Intro/approaches.tex b/org.eclipse.jubula.documentation/manual/en/tex/Introduction/Intro/approaches.tex
index 386e03650..3c7932e4f 100644
--- a/org.eclipse.jubula.documentation/manual/en/tex/Introduction/Intro/approaches.tex
+++ b/org.eclipse.jubula.documentation/manual/en/tex/Introduction/Intro/approaches.tex
@@ -25,7 +25,7 @@ Tests written in code also have the problem that they no longer view the softwar
\subsection{Recorded Tests}
-
+\label{IntroRecording}
Possibly the most popular approach to automated functional testing is macro recording, that is, recording a user's actions for later playback.
The appeal of this approach is the apparently quick success that can be seen: a test script can be quickly recorded and played back, giving the impression that automated testing is nothing more than recording a manual test.

Back to the top