diff options
-rw-r--r-- | lldb/test/foundation/TestObjCMethods.py | 2 | ||||
-rw-r--r-- | lldb/test/lldbtest.py | 4 |
2 files changed, 4 insertions, 2 deletions
diff --git a/lldb/test/foundation/TestObjCMethods.py b/lldb/test/foundation/TestObjCMethods.py index 9dd6650cf81..4494c1921b8 100644 --- a/lldb/test/foundation/TestObjCMethods.py +++ b/lldb/test/foundation/TestObjCMethods.py @@ -109,7 +109,7 @@ class FoundationTestCase(TestBase): substrs = ["ARG: (MyString *) self", "ARG: (struct objc_selector *) _cmd"]) - self.expect("expr self->non_existent_member", VARIABLES_DISPLAYED_CORRECTLY, error=True, + self.expect("expr self->non_existent_member", COMMAND_FAILED_AS_EXPECTED, error=True, startstr = "error: 'MyString' does not have a member named 'non_existent_member'") self.expect("frame variable self->str", VARIABLES_DISPLAYED_CORRECTLY, diff --git a/lldb/test/lldbtest.py b/lldb/test/lldbtest.py index b8108c355dc..65807c703cb 100644 --- a/lldb/test/lldbtest.py +++ b/lldb/test/lldbtest.py @@ -113,6 +113,8 @@ else: # Some commonly used assert messages. # +COMMAND_FAILED_AS_EXPECTED = "Command has failed as expected" + CURRENT_EXECUTABLE_SET = "Current executable set successfully" PROCESS_IS_VALID = "Process is valid" @@ -408,7 +410,7 @@ class TestBase(unittest2.TestCase): If the keyword argument error is set to True, it signifies that the API client is expecting the command to fail. In this case, the error stream - from running the command is retrieved and compared againt the golden + from running the command is retrieved and compared against the golden input, instead. """ trace = (True if traceAlways else trace) |