aboutsummaryrefslogtreecommitdiffstats
path: root/lib/common_test/doc/src/cover_chapter.xml
diff options
context:
space:
mode:
authorKenneth Lundin <[email protected]>2013-08-29 11:56:20 +0200
committerKenneth Lundin <[email protected]>2013-08-29 11:56:20 +0200
commitfc13629197e7c3698ff0739b51d8219069444dec (patch)
tree2a86d1b3abb93df54a9c38db19a06a4cd36733a9 /lib/common_test/doc/src/cover_chapter.xml
parent7d658d12f2ff5d9fedd193b0eb4076871b602425 (diff)
downloadotp-fc13629197e7c3698ff0739b51d8219069444dec.tar.gz
otp-fc13629197e7c3698ff0739b51d8219069444dec.tar.bz2
otp-fc13629197e7c3698ff0739b51d8219069444dec.zip
Corrections so that the documentation confirms to the DTD
Diffstat (limited to 'lib/common_test/doc/src/cover_chapter.xml')
-rw-r--r--lib/common_test/doc/src/cover_chapter.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/common_test/doc/src/cover_chapter.xml b/lib/common_test/doc/src/cover_chapter.xml
index 736486350b..b952df58f1 100644
--- a/lib/common_test/doc/src/cover_chapter.xml
+++ b/lib/common_test/doc/src/cover_chapter.xml
@@ -94,7 +94,7 @@
<p><c>$ ct_run -dir $TESTOBJS/db -cover $TESTOBJS/db/config/db.coverspec</c></p>
<p>You may also pass the cover specification file name in a
- call to <c><seealso marker="ct#run_test-1">ct:run_test/1</seealso></c>, by adding a <c>{cover,CoverSpec}</c>
+ call to <seealso marker="ct#run_test-1"><c>ct:run_test/1</c></seealso>, by adding a <c>{cover,CoverSpec}</c>
tuple to the <c>Opts</c> argument. Also, you can of course
enable code coverage in your test specifications (read
more in the chapter about
@@ -102,8 +102,8 @@
specifications</seealso>).</p>
</section>
- <marker id="cover_stop"></marker>
<section>
+ <marker id="cover_stop"></marker>
<title>Stopping the cover tool when tests are completed</title>
<p>By default the Cover tool is automatically stopped when the
tests are completed. This causes the original (non cover
@@ -120,8 +120,8 @@
<p>The option can be set by using the <c>-cover_stop</c> flag with
<c>ct_run</c>, by adding <c>{cover_stop,true|false}</c> to the
- Opts argument to <c><seealso
- marker="ct#run_test-1">ct:run_test/1</seealso></c>, or by adding
+ Opts argument to <seealso
+ marker="ct#run_test-1"><c>ct:run_test/1</c></seealso>, or by adding
a <c>cover_stop</c> term in your test specification (see chapter
about <seealso
marker="run_test_chapter#test_specifications">test
@@ -189,8 +189,8 @@
specification file for Common Test).</p>
</section>
- <marker id="cross_cover"/>
<section>
+ <marker id="cross_cover"/>
<title>Cross cover analysis</title>
<p>The cross cover mechanism allows cover analysis of modules
across multiple tests. It is useful if some code, e.g. a library