This issue outlines a need to automatically test this package using GitHub Actions on pull request (PR) or pushes to the main branch. Adding automated tests will help observe passing or failing tests from the repository, making these findings openly informing developers or people using the package. As a side-effect, accomplishing work related to this issue will help form documented technical agreement (via source code) about how tests should be run among the maintainers (including any nuances which could be outlined in comments / docs).
I feel this should be a prerequisite of #52 in order to ensure stability of related changes. Leveraging automated tests in this way would effectively show a "before" and "after" for that issue (and others).
This issue outlines a need to automatically test this package using GitHub Actions on pull request (PR) or pushes to the
mainbranch. Adding automated tests will help observe passing or failing tests from the repository, making these findings openly informing developers or people using the package. As a side-effect, accomplishing work related to this issue will help form documented technical agreement (via source code) about how tests should be run among the maintainers (including any nuances which could be outlined in comments / docs).I feel this should be a prerequisite of #52 in order to ensure stability of related changes. Leveraging automated tests in this way would effectively show a "before" and "after" for that issue (and others).