You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/contributing.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,7 +143,7 @@ Zarr strives to maintain 100% test coverage under the latest Python stable relea
143
143
hatch env run --env test.py3.12-2.2-optional run-coverage
144
144
```
145
145
146
-
will automatically run the test suite with coverage and produce a XML coverage report. This should be 100% before code can be accepted into the main code base.
146
+
will automatically run the test suite with coverage and produce an XML coverage report. This should be 100% before code can be accepted into the main code base.
147
147
148
148
You can also generate an HTML coverage report by running:
149
149
@@ -273,4 +273,4 @@ performance benchmarks as part of our test suite. The benchmarks can be are foun
273
273
By default pytest is configured to run these benchmarks as plain tests (i.e., no benchmarking). To run
274
274
a benchmark with timing measurements, use the `--benchmark-enable` when invoking `pytest`.
275
275
276
-
The benchmarks are run as part of the continuous integration suite through [codspeed](https://codspeed.io/zarr-developers/zarr-python).
276
+
The benchmarks are run as part of the continuous integration suite through [codspeed](https://codspeed.io/zarr-developers/zarr-python).
0 commit comments