Refactor Scoreswrapper CubeList code out into a fixture
- Dominant language
- Python
- Stars
- 33
- Forks
- 19
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 30
Description
> We should move this code out into a [pytest fixture](https://docs.pytest.org/en/stable/how-to/fixtures.html) within this file and use it across multiple tests. That should make our tests faster and only dependent on what they actually need.
_Originally posted by @jfrost-mo in [#2232](https://github.com/MetOffice/CSET/pull/2232/changes#r3520101940)_
Contributor guide
No contributing guide indexed for this repository
Research direction
Find the test file containing the Scoreswrapper CubeList setup and read pytest's fixture guidance first. Extract the setup into a fixture in that file, reuse it across the relevant tests, and run those tests to confirm they pass with only the required dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100