commit: ed27d8b692bf5adc0aa96074124c3150220bc7ee Author: Michał Górny <mgorny <AT> gentoo <DOT> org> AuthorDate: Fri Dec 11 21:32:46 2020 +0000 Commit: Michał Górny <mgorny <AT> gentoo <DOT> org> CommitDate: Fri Dec 11 21:32:46 2020 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ed27d8b6
dev-python/exam: Fix metadata.xml indent Signed-off-by: Michał Górny <mgorny <AT> gentoo.org> dev-python/exam/metadata.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/dev-python/exam/metadata.xml b/dev-python/exam/metadata.xml index 6a0cf120810..d79043f73e5 100644 --- a/dev-python/exam/metadata.xml +++ b/dev-python/exam/metadata.xml @@ -18,9 +18,9 @@ Exam is a Python toolkit for writing better tests. It aims to remove a lot of th Aside from the obvious "does the code work?", writings tests has many additional goals and benefits: - If written semantically, reading tests can help demonstrate how the code is supposed to work to other developers. - If quick running, tests provide feedback during development that your changes are working or not having an adverse side effects. - If they're easy to write correctly, developers will write more tests and they will be of a higher quality. + If written semantically, reading tests can help demonstrate how the code is supposed to work to other developers. + If quick running, tests provide feedback during development that your changes are working or not having an adverse side effects. + If they're easy to write correctly, developers will write more tests and they will be of a higher quality. Unfortunately, the common pattern for writing Python unit tests tends to not offer any of these advantages. Often times results in inefficient and unnecessarily obtuse testing code. Additionally, common uses of the mock library can often result in repetitive boiler-plate code or inefficiency during test runs.
