From f4a84a8dfd59220fc6f49ab4d29688b28564a2e6 Mon Sep 17 00:00:00 2001 From: mei-li Date: Thu, 15 Aug 2019 18:12:18 +0200 Subject: [PATCH 1/2] reword a parametrize example sentence --- doc/en/example/parametrize.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/en/example/parametrize.rst b/doc/en/example/parametrize.rst index 1e6d53e37..387e3f9de 100644 --- a/doc/en/example/parametrize.rst +++ b/doc/en/example/parametrize.rst @@ -262,8 +262,8 @@ Deferring the setup of parametrized resources The parametrization of test functions happens at collection time. It is a good idea to setup expensive resources like DB connections or subprocess only when the actual test is run. -Here is a simple example how you can achieve that, first -the actual test requiring a ``db`` object: +Here is a simple example how you can achieve that. This test +requires a ``db`` object fixture: .. code-block:: python From d50198a3ff1458b6b175cb9ae274a5a98be965ab Mon Sep 17 00:00:00 2001 From: Daniel Hahler Date: Thu, 15 Aug 2019 23:54:03 +0200 Subject: [PATCH 2/2] ci: add codecov.yml to turn comments off The only benefit for me is to get notified about finished builds, but that might happen to early anyway. Apart from that they are rather big and distract from actual comments. --- codecov.yml | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 codecov.yml diff --git a/codecov.yml b/codecov.yml new file mode 100644 index 000000000..a0a308588 --- /dev/null +++ b/codecov.yml @@ -0,0 +1,7 @@ +coverage: + status: + project: true + patch: true + changes: true + +comment: off