[Lldb-commits] [lldb] r117153 - /lldb/trunk/docs/testsuite/a-detailed-walkthrough.txt

[Johnny Chen]

Author: johnny
Date: Fri Oct 22 16:37:51 2010
New Revision: 117153

URL: http://llvm.org/viewvc/llvm-project?rev=117153&view=rev
Log:
Just use 'test harness', not 'test harness runtime'.

Modified:
    lldb/trunk/docs/testsuite/a-detailed-walkthrough.txt

Modified: lldb/trunk/docs/testsuite/a-detailed-walkthrough.txt
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/docs/testsuite/a-detailed-walkthrough.txt?rev=117153&r1=117152&r2=117153&view=diff
==============================================================================
--- lldb/trunk/docs/testsuite/a-detailed-walkthrough.txt (original)
+++ lldb/trunk/docs/testsuite/a-detailed-walkthrough.txt Fri Oct 22 16:37:51 2010
@@ -153,12 +153,12 @@
     mydir = "settings"
 
 which happens right after the SettingsCommandTestCase class declaration comes
-into place.  It specifies the relative directory to the top level 'test' so that
-the test harness runtime can change its working directory in order to find the
-executable as well as the source code files.  The runCmd() method is defined
-in the TestBase base class (within test/lldbtest.py) and its purpose is to pass
-the specified command to the lldb command interpreter.  It's like you're typing
-the command within an interactive lldb session.
+into place. It specifies the relative directory to the top level 'test' so that
+the test harness can change its working directory in order to find the
+executable as well as the source code files. The runCmd() method is defined in
+the TestBase base class (within test/lldbtest.py) and its purpose is to pass the
+specified command to the lldb command interpreter. It's like you're typing the
+command within an interactive lldb session.
 
 The CURRENT_EXECUTABLE_SET is an assert message defined in the lldbtest module
 so that it can be reused from other test modules.