Skip to content
Anslation

Release smoke checks that run when your pipeline says so.

AnsBot runs release smoke checks from your pipeline: after a release your pipeline sends one HTTPS POST with the bot's webhook token, and AnsBot opens your key pages in a browser, checks that the right text appears and captures screenshots. When it finishes, a callback, signed when you add a signing key, tells your pipeline whether the run succeeded or failed.

Wire a smoke check into a release. Five steps.

  1. Build the check bot

    Go to your key pages, verify the text that proves each one works, and take screenshots.

  2. Create a webhook endpoint

    Copy its token, shown when you create or rotate it.

  3. Call it after deploy

    Your pipeline sends an HTTPS POST with the token; the JSON body can carry inputs such as the site address.

  4. Get the result

    A callback brings the run's status, succeeded or failed, to your pipeline, signed when you add a signing key.

  5. Read a failure

    The failed step's screenshot, a checkpoint and a private trace show what broke.

A typical smoke check. An example bot.

Example AnsBot smoke check
StepStep typeWhat it checks
Open the home pageGo to URLThe site answers at {{site_url}}.
Confirm the home pageVerify textThe page shows your headline.
Open the sign-in pageClickThe sign-in link works.
Confirm the sign-in formVerify textThe form's heading appears.
Keep proofScreenshotA full-page image for the run.

An example: change the pages and texts to your own.

What a smoke check is not. Know the edges.

It does

  • Fails the run, with a screenshot, when a verify step does not find its text.
  • Checks whichever address your pipeline sends as an input.

It does not

  • Reach a staging site on a private network: it must be reachable on the public internet.
  • Measure page speed or performance.
  • Run your own test code.
  • Run several browsers at once for one check.

Tips for your pipeline. Three habits.

  • Keep the token safeStore the webhook token in your pipeline's protected settings, and rotate it if it leaks.
  • Pass the address as an inputSend the site address as an input, so one bot can check staging and production.
  • Check the signatureGive the endpoint a signing key, then check the X-Ansbot-Signature header before you trust the result.

Smoke checks: questions.

Still have a question? Ask us

Can AnsBot run a check after every deploy?

Yes. Your pipeline sends one HTTPS POST to the bot's webhook endpoint with its token, and AnsBot queues a run that opens your pages and checks them.

How does my pipeline learn the result?

From a callback: when the run ends, AnsBot posts its result and status to your endpoint, signed with HMAC-SHA256 in the X-Ansbot-Signature header when the endpoint has a signing key.

Can the check run against a staging site?

Yes, if the staging site is reachable on the public internet: send its address as an input in the webhook's JSON body. Private and internal addresses are refused.

Does this replace an automated test suite?

No. It is a handful of browser checks with evidence (visible text, screenshots and a pass or fail), not a framework for writing tests in code.

Check every release in a real browser.

Tell us the web task and the site it runs on. We read every request and reply by email.

Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838