More comprehensive testing (coverage etc.) for cyclicity
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 150
- Forks
- 23
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 2
Description
As highlighted in https://github.com/NCAS-CMS/cf-python/issues/851#issuecomment-2710845319, in the past year or so there have been several bugs and deficiencies detected and fixed relating to the concept of cyclic domain axes, and though the fixing PRs have included testing to isolate said issues to improve the level of testing, it is probable we could do with better testing since issues have congregated for the concept.
So, we should review areas where cyclicity should be covered in the tests but is not at present, and add sufficient testing in each such case.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the cyclic-domain-axis bugs and fixes referenced from issue #851, then inspect the existing test coverage for cyclicity throughout the project. Identify uncovered areas and add tests for each relevant case; done means cyclicity behavior is comprehensively exercised without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100