or even write new tests at all, PTVS is an indispensable debugging
extension to VS that enables full editing and debugging support for Python
(including mixed native/managed debugging).
-* `SWIG for Windows <http://www.swig.org/download.html>_`
+* `SWIG for Windows <http://www.swig.org/download.html>`_
The steps outlined here describes how to set up your system and install the
required dependencies such that they can be found when needed during the build
time (e.g., C and C++) there is also usually no process necessary to test
the `SBType`-related parts of the API. With those languages it's also
possible to test `SBValue` by running expressions with
- `SBTarget.EvaluateExpression` or the `expect_expr` testing utility.
+ `SBTarget.EvaluateExpression` or the ``expect_expr`` testing utility.
Functionality that always requires a running process is everything that
tests the `SBProcess`, `SBThread`, and `SBFrame` classes. The same is true
self.expect_expr("2 + 2", result_value="0")
**Prefer using specific asserts over the generic assertTrue/assertFalse.**.
- The `self.assertTrue`/`self.assertFalse` functions should always be your
+ The ``self.assertTrue``/``self.assertFalse`` functions should always be your
last option as they give non-descriptive error messages. The test class has
- several expressive asserts such as `self.assertIn` that automatically
+ several expressive asserts such as ``self.assertIn`` that automatically
generate an explanation how the received values differ from the expected
- ones. Check the documentation of Python's `unittest` module to see what
+ ones. Check the documentation of Python's ``unittest`` module to see what
asserts are available. LLDB also has a few custom asserts that are tailored
to our own data types.
+-----------------------------------------------+-----------------------------------------------------------------+
-| **Assert** | **Description** |
+| **Assert** | **Description** |
+-----------------------------------------------+-----------------------------------------------------------------+
-| ``assertSuccess`` | Assert that an ``lldb.SBError`` is in the "success" state. |
+| ``assertSuccess`` | Assert that an ``lldb.SBError`` is in the "success" state. |
+-----------------------------------------------+-----------------------------------------------------------------+
-| ``assertState`` | Assert that two states (``lldb.eState*``) are equal. |
+| ``assertState`` | Assert that two states (``lldb.eState*``) are equal. |
+-----------------------------------------------+-----------------------------------------------------------------+
| ``assertStopReason`` | Assert that two stop reasons (``lldb.eStopReason*``) are equal. |
+-----------------------------------------------+-----------------------------------------------------------------+
If you can't find a specific assert that fits your needs and you fall back
to a generic assert, make sure you put useful information into the assert's
- `msg` argument that helps explain the failure.
+ ``msg`` argument that helps explain the failure.
::
alias lldb self.dbg.HandleCommand("%*")
-::
-
Debugging Test Failures on Windows
``````````````````````````````````