Remove Iris' TestRunner #5205
Merged
Remove Iris' TestRunner #5205
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #5205 +/- ##
=======================================
Coverage 89.27% 89.27%
=======================================
Files 88 88
Lines 22258 22258
Branches 4867 4867
=======================================
Hits 19871 19871
Misses 1641 1641
Partials 746 746
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
lbdreyer
added a commit
to lbdreyer/iris
that referenced
this pull request
Mar 24, 2023
lbdreyer
added a commit
to lbdreyer/iris
that referenced
this pull request
Mar 24, 2023
lbdreyer
added a commit
to lbdreyer/iris
that referenced
this pull request
Mar 24, 2023
tkknight
added a commit
to tkknight/iris
that referenced
this pull request
Apr 4, 2023
* upstream/main: (274 commits) Cf cell method (SciTools#5224) Bump scitools/workflows from 2023.03.3 to 2023.04.1 (SciTools#5231) [pre-commit.ci] pre-commit autoupdate (SciTools#5230) Bump scitools/workflows from 2023.03.2 to 2023.03.3 (SciTools#5227) raise dask min pin (SciTools#5225) Enable lazy computation of wind vector rotation (SciTools#4972) Benchmark runner script (SciTools#5215) add locks readme (SciTools#5222) use explicit version for ci refresh-lockfiles gha (SciTools#5221) SciTools#5180 do not run publish-to-test-pypi on forks (SciTools#5220) Fix Makefile for consequences of SciTools#5204. (SciTools#5217) Bump actions/stale from 7 to 8 (SciTools#5208) Remove Iris' TestRunner (SciTools#5205) standardize requirements structure (SciTools#5204) Updated environment lockfiles (SciTools#5199) Add histogram convenience for passing Iris objects to plt.hist (SciTools#5189) Updated environment lockfiles (SciTools#5192) announce new contributor in whatsnew (SciTools#5198) iris.util.new_axis anonymous new dimension fix (SciTools#5194) Lockfiles and pydata-sphinx-theme fix (SciTools#5188) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #5173
The iris.tests.runner had various functionality. If we remove it we can replace it with the alternative listed below
nox --session testspytest lib/iris/testsnox --session gallerypytest docs/gallery_testspytest lib/iris/tests/system_test.pynox --session tests --coveragepytest lib/iris/tests --cov=lib/irisexport IRIS_TEST_CREATE_MISSING=True nox --session testsexport IRIS_TEST_CREATE_MISSING=True pytest lib/iris/testsauto)pytest -n 2 lib/iris/testspytest -x lib/iris/testsBefore doing this, I didn't even realise the test runner had all these options, e.g. I have always manually set
IRIS_TEST_CREATE_MISSINGThere is not a direct alternative for every option. For example --no-data doesn't really have an alternative, but I can't really see the use case for this. At a later stage we could consider controlling this with pytest markers.