Any new PR should be accompanied by relevant tests. However, large portions of the libraries are as of yet untested. Any PRs improving test coverage of existing code are welcome.
Keep the following things in mind when creating tests:
- Follow existing practices to keep the style of tests consistent. This is a good example to start from.
- Consider using property tests wherever possible, as they ensure our code does not only work for a set of hand-picked values.
- Focus on testing behaviours rather than specific members.
- Refactoring code as part of adding tests is allowed and encouraged, though consider verifying breaking changes before making them.
- Consider creating a draft PR before starting to indicate you are working on the tests for a specific class. Likewise, check if there aren't any open PRs for the class you want to test ahead of starting work.
If you are unsure what class to test, but are interested to help, feel free to reply below and we're happy to get you going.
Any new PR should be accompanied by relevant tests. However, large portions of the libraries are as of yet untested. Any PRs improving test coverage of existing code are welcome.
Keep the following things in mind when creating tests:
If you are unsure what class to test, but are interested to help, feel free to reply below and we're happy to get you going.