Semantic tests require LLMs, and therefore run locally for now. Add a badge to README that shows if they passed, "outdated" otherwise.
Could be using a local generator such as pytest-local-badge which switches to green once the tests have passed locally, in full or percentage.
- prior to a commit, the badge is "outdated" or "no status"
- tests run, and change the badge to green.
Unfortunately that creates noise in the git log. An idea:
Dev runs tests -> tests.svg updates locally. Dev runs git commit. The hook does nothing if the tests just passed; it only resets to "outdated" if the tests weren't run.
The badge status is tied to the Commit SHA. At main, we see the status of main. On a feature-branch, we see the status of that branch.
Semantic tests require LLMs, and therefore run locally for now. Add a badge to README that shows if they passed, "outdated" otherwise.
Could be using a local generator such as pytest-local-badge which switches to green once the tests have passed locally, in full or percentage.
Unfortunately that creates noise in the git log. An idea:
Dev runs tests -> tests.svg updates locally. Dev runs git commit. The hook does nothing if the tests just passed; it only resets to "outdated" if the tests weren't run.
The badge status is tied to the Commit SHA. At main, we see the status of main. On a feature-branch, we see the status of that branch.