Consider using `chex` in validation and/or testing
Open
Nobody has claimed this yet.
discussion
request
testing
- Dominant language
- Python
- Stars
- 29
- Forks
- 9
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 8
Description
https://github.com/google-deepmind/chex
Could be helpful for improve, e.g. assertions about shapes:
Contributor guide
No contributing guide indexed for this repository
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 reading the linked chex project and the referenced test_first_difference_ar.py example, then inspect PyRenew's existing validation and test structure. Define which assertions or validation paths should use chex and document the intended scope; done means the selected checks are integrated and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100