diff options
author | Siri Hansen <[email protected]> | 2016-03-10 14:55:22 +0100 |
---|---|---|
committer | Siri Hansen <[email protected]> | 2016-03-10 14:55:22 +0100 |
commit | e3e55881b15757e15ea1995b0f8dbfd305f9e89d (patch) | |
tree | a4379d63af0feefb52542f69511272b70389ce4c /lib/common_test/doc/src/dependencies_chapter.xml | |
parent | 5fa1dff3c9f92a3b7c6a897af32c0c72a9a9e8a7 (diff) | |
parent | 880280b22f30a5ba67dcbd93bf85e14c04acc25b (diff) | |
download | otp-e3e55881b15757e15ea1995b0f8dbfd305f9e89d.tar.gz otp-e3e55881b15757e15ea1995b0f8dbfd305f9e89d.tar.bz2 otp-e3e55881b15757e15ea1995b0f8dbfd305f9e89d.zip |
Merge branch 'siri/common_test/fix-doc-links' into maint
* siri/common_test/fix-doc-links:
Fix link errors in common_test documentation
Document that any ssh option is allowed in ct_netconfc
Conflicts:
lib/common_test/doc/src/ct_hooks_chapter.xml
lib/common_test/doc/src/ct_netconfc.xml
Diffstat (limited to 'lib/common_test/doc/src/dependencies_chapter.xml')
-rw-r--r-- | lib/common_test/doc/src/dependencies_chapter.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/common_test/doc/src/dependencies_chapter.xml b/lib/common_test/doc/src/dependencies_chapter.xml index d96a41473f..29c54e819a 100644 --- a/lib/common_test/doc/src/dependencies_chapter.xml +++ b/lib/common_test/doc/src/dependencies_chapter.xml @@ -87,8 +87,8 @@ <p>To avoid this, we can consider starting and stopping the server for every test. We can thus implement the start and stop action as common functions to be called from - <seealso marker="common_test_app#Module:init_per_testcase-2"><c>init_per_testcase</c></seealso> and - <seealso marker="common_test_app#Module:end_per_testcase-2"><c>end_per_testcase</c></seealso>. + <seealso marker="common_test#Module:init_per_testcase-2"><c>init_per_testcase</c></seealso> and + <seealso marker="common_test#Module:end_per_testcase-2"><c>end_per_testcase</c></seealso>. (Remember to test the start and stop functionality separately.) The configuration can also be implemented as a common function, maybe grouped with the start function. Finally, the testing of connecting and disconnecting a @@ -194,9 +194,9 @@ <p>To pass data from one test suite to another, the same mechanism is used. The data is to be saved by finction - <seealso marker="common_test_app#Module:end_per_suite-1"><c>end_per_suite</c></seealso> + <seealso marker="common_test#Module:end_per_suite-1"><c>end_per_suite</c></seealso> and read by function - <seealso marker="common_test_app#Module:init_per_suite-1"><c>init_per_suite</c></seealso> + <seealso marker="common_test#Module:init_per_suite-1"><c>init_per_suite</c></seealso> in the suite that follows. When passing data between suites, <c>Saver</c> carries the name of the test suite.</p> @@ -306,7 +306,7 @@ any property, that is, they are not required to also be sequences. If you want the status of the subgroup to affect the sequence on the level above, return <c>{return_group_result,Status}</c> from - <seealso marker="common_test_app#Module:end_per_group-2"><c>end_per_group/2</c></seealso>, + <seealso marker="common_test#Module:end_per_group-2"><c>end_per_group/2</c></seealso>, as described in section <seealso marker="write_test_chapter#repeated_groups">Repeated Groups</seealso> in Writing Test Suites. |