From fecda0306636345712f5d53d073b6489e8d997a7 Mon Sep 17 00:00:00 2001 From: Sachidananda Urs Date: Fri, 6 Jul 2018 17:37:57 +0530 Subject: [PATCH] Fix typos in documentation (#42406) Fix typos in unit test documentation Fixes: #42405 --- docs/docsite/rst/dev_guide/testing_units.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/dev_guide/testing_units.rst b/docs/docsite/rst/dev_guide/testing_units.rst index a7df079d98f..6d484edc8db 100644 --- a/docs/docsite/rst/dev_guide/testing_units.rst +++ b/docs/docsite/rst/dev_guide/testing_units.rst @@ -103,7 +103,7 @@ Here is an example of a function:: Here is an example of a class:: - import unittest: + import unittest class AddTester(unittest.TestCase) @@ -127,7 +127,7 @@ few basic tests for a module. The class-based test allows more tidy set up and of pre-requisites, so if you have many test cases for your module you may want to refactor to use that. -Assertions using the simple ``assert`` function inside the tests will give give full +Assertions using the simple ``assert`` function inside the tests will give full information on the cause of the failure with a trace-back of functions called during the assertion. This means that plain asserts are recommended over other external assertion libraries.