-
Testing
Make my tests run automatically on every push
Set up CI so the test suite runs on every commit and pull request, with failures blocking merges.
Free Prompt
My tests only run when I remember to run them, which means they effectively don't run. I want them running automatically on every push.
Set up CI for my repo (GitHub Actions if I'm on GitHub, or the equivalent for my host; check what's already configured first):
1. Run the full test suite on every push to main and on every pull request.
2. Install dependencies from the lockfile, set up the test database or services my suite needs, and fail the build loudly when any test fails.
3. Cache dependencies so runs are fast enough that I don't start hating them.
4. Report status back to pull requests so a failing suite blocks merging (or at least shows a red X I'll have to consciously ignore).
If my suite needs secrets or environment variables in CI, use the CI system's secret storage, and make sure test values are used, never production credentials.
Keep the CI config minimal and readable. One job that runs the suite is worth more than a pipeline with stages I don't need yet.
When done, show me the config, tell me how to verify it ran (I'll push a commit), and confirm what a failure looks like from my side.
What This Does / How This Helps
This sets up CI so your test suite runs on every push and pull request automatically, with failures visible before code reaches main. A test suite that depends on human memory decays within weeks. CI is what turns 'we have tests' into 'broken code doesn't ship,' which matters most precisely when you're moving fast and tired. It also makes the suite self-enforcing: nobody has to nag, the red X does the nagging.
Want to skip doing this by hand?
Fortivibe audits your app for all of the areas these prompts cover (and more).