diff options
| -rw-r--r-- | lldb/docs/testsuite/a-detailed-walkthrough.txt | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/lldb/docs/testsuite/a-detailed-walkthrough.txt b/lldb/docs/testsuite/a-detailed-walkthrough.txt index b29fcef289a..63c610e9286 100644 --- a/lldb/docs/testsuite/a-detailed-walkthrough.txt +++ b/lldb/docs/testsuite/a-detailed-walkthrough.txt @@ -153,12 +153,12 @@ class SettingsCommandTestCase(TestBase): 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. |
