Yes. ShipCheck is completely free with no signup, no watermarks, and no credit card required.

How is this different from TesterArmy or Playwright?

ShipCheck is a free, no-login tool for quick browser checks and visual diffs. Describe tests in plain English, get screenshots and reports instantly. Playwright is a framework you code against; ShipCheck handles the browser run for you.

Do I need to write code?

No. Write instructions in plain English like 'Click Get started' or 'Verify page contains Pricing'. ShipCheck converts them into browser actions automatically.

Are my tests stored on a server?

No. Test runs are ephemeral — results are returned to your browser and never permanently stored. Image uploads for visual diff are processed in-browser.

Can I compare screenshots too?

Yes. ShipCheck also includes a pixel-perfect visual diff tool — upload two images or paste two URLs to detect UI changes.

Yes. Notes on smoke tests and visual diffs are published at /blog on Tuesday and Thursday at 09:00 IST. A post stays unavailable until that time. The feed is /blog/feed.xml.

What sites can I test?

Any public HTTP/HTTPS website. In production, private IPs and localhost are blocked for security. When running ShipCheck locally (npm run dev), localhost URLs are allowed so you can test apps on your machine.

Sep 2026 · 4 min read

Trigger a smoke test from CI without a dashboard login

A token, a URL, and a JSON body are enough to fail a pipeline when the smoke test fails.

The browser UI is for a human pasting a URL. A pipeline wants the same run with a token and a status code. POST /api/browser-test/ci accepts a URL, optional mode and viewport, and returns ok, shareUrl, and the summary. A bad token is 401 and does not start Chromium.

Put CI_HOOK_TOKEN in the project secrets, send it as x-ci-token, and fail the job when ok is false. Pass notifyWebhook if Slack should see the share link. The quota on the hook is separate from the public browser-test limit, so a noisy deploy does not lock you out of the website.

Invalid JSON does not burn a quota slot. That detail is the same idea as public quotas: count the runs that actually cost a browser, not the typos.