-
Notifications
You must be signed in to change notification settings - Fork 297
Closed
Description
⚙ Feature Request
There are currently a few approaches to running the iris
tests as a developer:
- using the bespoke
iris.tests.runner
e.g.,python -m iris.tests.runner --default-tests
- using the
test
command fromsetuptools
e.g.,python setup.py test
- using
unittest
e.g.,python -m unittest discover iris
These are all perfectly functional approaches, for now, to take to run the iris
tests. However, there are a few problems with each approach, namely:
iris.tests.runner
mechanism is bespoke and heavily relies onnose
, which has been in maintenance mode for several years now i.e., it's dead-end technology 💣. Also using this mechanism is causing issues for automatically collating testing coverage statistics.- the use of the
test
command insetuptools
was deprecated in version41.5.0
, (latest50.3.0
) and will be withdrawn in a future version i.e., the future is closer than you think - ummm
unittest
isn'tpytest
, not even close 😉
Motivation
It's high time that iris
adoped a modern, robust, sustainable, actively supported and scalable approach to testing through pytest and pytest-xdist... before it's too late, and this becomes a much bigger issue than it needs to be i.e., let's agree to plan to avoid this crisis... before it's a crisis.
tkknight, bouweandela and rcomer