Right now the documentation is the only test of the code. For development purposes and to ensure robustness within the PReSto ecosystem, we need proper CI tests. I suggest:
- leveraging existing docs to generate CI tests.
- asking Claude to check coverage
- time the CI runtime to make sure it does not result in undue burden for PRs
Right now the documentation is the only test of the code. For development purposes and to ensure robustness within the PReSto ecosystem, we need proper CI tests. I suggest: