@@ -98,7 +98,7 @@ you can do something like the following::
98
98
To verify that your development environment is working, you can run the unit tests
99
99
for one of the test environments, e.g.::
100
100
101
- $ hatch env run --env test.py3.12-2.1-optional run
101
+ $ hatch env run --env test.py3.12-2.1-optional run-pytest
102
102
103
103
Creating a branch
104
104
~~~~~~~~~~~~~~~~~
@@ -140,7 +140,7 @@ Zarr includes a suite of unit tests. The simplest way to run the unit tests
140
140
is to activate your development environment
141
141
(see `creating a development environment `_ above) and invoke::
142
142
143
- $ hatch env run --env test.py3.12-2.1-optional run
143
+ $ hatch env run --env test.py3.12-2.1-optional run-pytest
144
144
145
145
All tests are automatically run via GitHub Actions for every pull
146
146
request and must pass before code can be accepted. Test coverage is
@@ -190,9 +190,13 @@ Both unit tests and docstring doctests are included when computing coverage. Run
190
190
191
191
$ hatch env run --env test.py3.12-2.1-optional run-coverage
192
192
193
- will automatically run the test suite with coverage and produce a coverage report.
193
+ will automatically run the test suite with coverage and produce a XML coverage report.
194
194
This should be 100% before code can be accepted into the main code base.
195
195
196
+ You can also generate an HTML coverage report by running::
197
+
198
+ $ hatch env run --env test.py3.12-2.1-optional run-coverage-html
199
+
196
200
When submitting a pull request, coverage will also be collected across all supported
197
201
Python versions via the Codecov service, and will be reported back within the pull
198
202
request. Codecov coverage must also be 100% before code can be accepted.
0 commit comments