Revision: 3722
Author: janne.t.harkonen
Date: Mon Jun 7 05:13:14 2010
Log: fixed link target
http://code.google.com/p/robotframework/source/detail?r=3722
Modified:
/trunk/doc/userguide/src/CreatingTestData/CreatingTestCases.txt
=======================================
--- /trunk/doc/userguide/src/CreatingTestData/CreatingTestCases.txt Mon
Jun 7 05:03:01 2010
+++ /trunk/doc/userguide/src/CreatingTestData/CreatingTestCases.txt Mon
Jun 7 05:13:14 2010
@@ -521,15 +521,15 @@
Setup and teardown are always a single keyword. If they need to take care
of multiple separate tasks, it is possible to create higher-level `user
keywords`_ for that purpose. An alternative solution is executing multiple
-keywords using the `Built-in keyword`_ :name:`Run Keywords` that was added
+keywords using the `BuiltIn keyword`_ :name:`Run Keywords` that was added
in Robot Framework 2.5.
-The test teardown is special in two ways. First of all, it is
-executed also when a test case fails, so it can be used for clean-up
-activities that must be done regardless of the test case status. Starting
from
-Robot Framework 2.5, all the keywords in the teardown are also executed
even
-if one of them fails. This `continue on failure`_ functionality can be used
-also with normal keywords, but inside teardowns it is on by default.
+The test teardown is special in two ways. First of all, it is executed also
+when a test case fails, so it can be used for clean-up activities that
must be
+done regardless of the test case status. Starting from Robot Framework
2.5, all
+the keywords in the teardown are also executed even if one of them fails.
This
+`continue on failure`_ functionality can be used also with normal
keywords, but
+inside teardowns it is on by default.
The easiest way to specify a setup or a teardown for test cases in a
test case file is using the :opt:`Test Setup` and :opt:`Test
