From 12f625e61b247f3e8f0b86f1b7939f36120748c2 Mon Sep 17 00:00:00 2001 From: BO ZHANG Date: Sat, 15 Oct 2022 14:28:45 +0800 Subject: [PATCH] updated unit test related terms --- doc/source/ch06_unittest.rst | 2 +- doc/source/ch09_build.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/ch06_unittest.rst b/doc/source/ch06_unittest.rst index e2cfdc4..b7f4c18 100644 --- a/doc/source/ch06_unittest.rst +++ b/doc/source/ch06_unittest.rst @@ -36,7 +36,7 @@ To run unit tests collected from directory ``.``, and calculate coverage for sou You will see messages like below -.. code-block:: plain +.. code-block:: none ============================ test session starts ============================ platform darwin -- Python 3.9.7, pytest-7.1.3, pluggy-0.13.1 diff --git a/doc/source/ch09_build.rst b/doc/source/ch09_build.rst index 9282a65..99a0880 100644 --- a/doc/source/ch09_build.rst +++ b/doc/source/ch09_build.rst @@ -67,7 +67,7 @@ The build log includes 6 sections. An example of test summary is at the end of build log (the attached ``build.zip``). If all checks/tests/validations passed, you will see a section as below. -.. code-block:: plain +.. code-block:: none ===================== TEST SUMMARY ===================== Test passed! @@ -85,7 +85,7 @@ Unit test coverage report The ``build log`` also contains a section of unit test coverage report. An example is below. -.. code-block:: plain +.. code-block:: none ---------- coverage: platform darwin, python 3.9.7-final-0 ----------- Name Stmts Miss Cover Missing -- GitLab