Private betaThis is the SIGSHIP beta. Everything here is live for testers; the public launch is in January.SIGSHIP private betaOpen the app →
  1. Home
  2. The 17 checks
  3. Nothing checks that a change did not break login
🧰 Launch hygiene · Nice to fix (SEV-3)

Nothing checks that a change did not break login 

In plain English: Nothing checks automatically that a change didn't break the most important parts of your app, like signing up, logging in and paying. A small fix can quietly break them.

What happens if you ship it

A small fix goes live on Friday and signup is broken until Monday.

How to fix it technical

Add one test for each money path: sign up, log in, and pay. Run them on every pull request.

Let your AI tool fix it

Paste this into Lovable, Bolt, Cursor, Replit or Claude Code:

Prompt for your AI tool
Fix this problem in my project: Nothing checks that a change did not break login. Add one test for each money path: sign up, log in, and pay. Run them on every pull request. Change only what this fix needs, then tell me what you changed and anything I have to do myself.

Check your app

Run npx sigship in your project folder. It reports this problem as no-tests, along with 16 other checks. Nothing leaves your computer. New to the terminal?

Questions

Which tests matter most?

One for each path that brings in money or users: sign up, log in and pay. A few tests there catch the breakages that hurt.

Can my AI tool write the tests?

Yes. Ask it for one end-to-end test for each of those paths, and to run them on every change.

See every check · Jargon, explained