aboutsummaryrefslogtreecommitdiff
path: root/lldb/docs/resources/test.rst
diff options
context:
space:
mode:
Diffstat (limited to 'lldb/docs/resources/test.rst')
-rw-r--r--lldb/docs/resources/test.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/lldb/docs/resources/test.rst b/lldb/docs/resources/test.rst
index 5275786..2b0e901 100644
--- a/lldb/docs/resources/test.rst
+++ b/lldb/docs/resources/test.rst
@@ -17,8 +17,8 @@ The LLDB test suite consists of three different kinds of test:
the output.
* **API tests**: Integration tests that interact with the debugger through the
SB API. These are written in Python and use LLDB's ``dotest.py`` testing
- framework on top of Python's `unittest2
- <https://docs.python.org/2/library/unittest.html>`_.
+ framework on top of Python's `unittest
+ <https://docs.python.org/3/library/unittest.html>`_.
All three test suites use ``lit`` (`LLVM Integrated Tester
<https://llvm.org/docs/CommandGuide/lit.html>`_ ) as the test driver. The test
@@ -94,7 +94,7 @@ programs from source, run them, and debug the processes.
As mentioned before, ``dotest.py`` is LLDB's testing framework. The
implementation is located under ``lldb/packages/Python/lldbsuite``. We have
several extensions and custom test primitives on top of what's offered by
-`unittest2 <https://docs.python.org/2/library/unittest.html>`_. Those can be
+`unittest <https://docs.python.org/3/library/unittest.html>`_. Those can be
found in
`lldbtest.py <https://github.com/llvm/llvm-project/blob/main/lldb/packages/Python/lldbsuite/test/lldbtest.py>`_.
@@ -146,7 +146,7 @@ the test should be run or not.
::
- @expectedFailure(checking_function_name)
+ @skipTestIfFn(checking_function_name)
In addition to providing a lot more flexibility when it comes to writing the
test, the API test also allow for much more complex scenarios when it comes to