From cb7519d9cea79d0713d5f6028bdc39b6a42439b2 Mon Sep 17 00:00:00 2001 From: Michal Petrik Date: Sat, 30 Apr 2022 13:38:02 +0200 Subject: [PATCH] Update 55_tests.md --- website/content/07_programs_libraries_modules/55_tests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/07_programs_libraries_modules/55_tests.md b/website/content/07_programs_libraries_modules/55_tests.md index e481cb9..a3429c6 100644 --- a/website/content/07_programs_libraries_modules/55_tests.md +++ b/website/content/07_programs_libraries_modules/55_tests.md @@ -172,7 +172,7 @@ Add this to your test file, run it, and you're off to the races. You can also sk Here, you don't need to make your test file runnable (by using `unittest.main()`), instead you're running `unittest` directly and telling it where to find your tests. {{% notice tip %}} -Use the `-v` (or `--verbose`) flag can give you more information about which tests were run +Using the `-v` (or `--verbose`) flag can give you more information about which tests were run {{% /notice %}} @@ -218,4 +218,4 @@ Subclassing the TestCase class gives you a bunch of useful assertions that you c ### Growing your Tests -Standard `unittest` tests are fine for most projects. As your programs grow and organization becomes more complex, you might want to consider an alternative testing framework or test runner. The 3rd party `nose2` and `pytest` modules are compatible with `unittest` but do things slightly differently. You can find more information in the [nose2 documentation](https://nose2.readthedocs.io/en/latest/) and [pytest documentation](https://docs.pytest.org/en/latest/). \ No newline at end of file +Standard `unittest` tests are fine for most projects. As your programs grow and organization becomes more complex, you might want to consider an alternative testing framework or test runner. The 3rd party `nose2` and `pytest` modules are compatible with `unittest` but do things slightly differently. You can find more information in the [nose2 documentation](https://nose2.readthedocs.io/en/latest/) and [pytest documentation](https://docs.pytest.org/en/latest/).