TST: include mock classes into coverage run
- Dominant language
- Python
- Stars
- 88
- Forks
- 64
- Avg merge
- 38m
- Merged PRs (30d)
- 1
Description
It seems like that some of the mock classes we use in tests are extremely detailed, yet the nuances are not used in the tests creating the impression we cover more corner cases than we actually do.
With a bit of file restructuring, I expect that it would be possible to include those classes into the coverage run, (or have a second coverage run that only runs for the test mocks?, details TBD)
https://github.com/astropy/pyvo/pull/432#issuecomment-1458533896
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the test mock classes and the repository's current coverage configuration, then trace which mock behavior is currently excluded. Determine whether restructuring or a separate mock-focused coverage run is appropriate; done means the detailed mock behavior is exercised and the coverage results no longer imply untested corner cases are covered.
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
- 35/100