maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Just use 'test harness', not 'test harness runtime'. 

llvm-svn: 117153
This commit is contained in:
Johnny Chen 2010-10-22 21:37:51 +00:00
parent f4f70bb890
commit f3f1e00e24
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
lldb/docs/testsuite/a-detailed-walkthrough.txt
View File

@ -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.