Cookies on AIGROW

We use necessary cookies to run the site. With your permission, we also use cookies for analytics, session recordings and marketing attribution.

Cookie Policy

Automated browser tests for your site or web app: Playwright tests for up to 8 key journeys, run in your own CI on every deploy

$990Fixed price, paid onceWithin 10 working days of your answers and access

Order for $990How it works

Every change reaches you as a pull request you merge, and the code is yours. Delivered as listed, or refunded in full.

AIGROW writes Playwright tests that drive a real browser through up to 8 key journeys of your site or web app, such as sign-up, log-in, search, cart, checkout in your payment provider’s test mode and contact forms, for $990 paid once. They run in your own GitHub Actions or GitLab CI on every deploy or on a schedule.

What the browser tests do, and what they do not

A browser test opens your site in a real browser and does what a visitor does: it fills in forms, clicks, and checks what the page shows at the end. We write one test for each journey you pick, up to 8, with Playwright, an open source testing tool from Microsoft.

What it does
  • Writes one Playwright test for each journey you pick, up to 8, such as sign-up, log-in, search, cart, checkout and contact forms
  • Runs a checkout only through your payment provider’s test mode, such as Stripe test mode or the PayPal sandbox
  • Runs the tests in Chromium, and also in Firefox and WebKit, the engine behind Safari, if you ask
  • Sets up a workflow in your GitHub Actions or GitLab CI that runs the tests on every deploy, on a schedule, or both
  • Saves the test report of every run in your CI, with a trace of each failed test that shows the step where it stopped
  • Keeps test logins in your CI’s secrets, never in the code
  • Writes a short readme on how to run the tests, read a failure and add a journey
  • Sends every change as a pull request, a merge request on GitLab, for you to review and merge
What it does not do
  • It does not test against real customer accounts: only your staging site, or test accounts you give us
  • It does not make live payments: payments run only in your provider’s test mode
  • It does not load test your site or measure how much traffic it can take
  • It does not test your security: no scans, no attacks, no attempts to get past a login
  • It does not scrape or test sites that are not yours
  • It does not promise to find every bug: a test checks the journey it was written for, and nothing else
  • It does not fix your site: when a test shows a break, we tell you where, and the fix is yours
  • It does not need a call: the questions are written and the rest is email and pull requests

From payment to tests in your CI

Each step and when it happens. No call, and nothing reaches your main branch unless you merge it.

Pay at checkoutPay once by card at the Stripe checkout. Stripe sends the receipt.2 minutes
Answer the questionnaireWe email you a short questionnaire straight after payment: your site and staging address, the journeys to test, your payment provider and your CI.About 20 minutes
Give us test accessSend a test account for each role in a separate email, and add our account to the repository with read access: Read on GitHub, Reporter on GitLab. The 10 working days start once we have your answers and access.10 minutes
We write the testsWe write one Playwright test for each journey, run them against your staging site until each one passes, and set up the workflow in your CI.Within 10 working daysAfter your answers and access
Review and mergeYou get a pull request with the tests, the workflow and the readme. Once you merge it, the tests run in your CI. The maintenance link comes with the handover, if you want it.When you merge

Up to 8 journeys, one price

Paid once at checkout, which asks for your email and card. One order covers one site or web app and one repository. Right after payment we email you a short questionnaire. Maintenance is optional and starts at handover.

What we need from you

Reply to our questionnaire with your site and its staging address, up to 8 journeys, a test account for each role they need, your payment provider in test mode, your CI and the repository for the tests. Then add our GitHub or GitLab account to that repository with read access. We never ask for a real customer’s login or a password to your live admin.

What you receive

  • One Playwright test for each journey you pick, up to 8
  • A CI workflow for GitHub Actions or GitLab CI that runs the tests on every deploy, on a schedule, or both
  • A test report and a trace of each failed test, saved with every run in your CI
  • A short readme: how to run the tests, read a failure and add a journey
  • All of it in your repository as a pull request you merge, and the code yours

Automated browser tests

$990

Paid once at checkout. No subscription, nothing renews.

Maintenance, monthlyBilled monthly

Optional, once your tests are handed over: we read your test runs every week, update the tests your site’s changes break within 2 working days, and add one new journey a month, each as a pull request you merge. The link also comes with the handover. Cancel any time; maintenance stops at the end of the paid month.

$149

Billed every month from checkout. Cancel any time from the link in every email we send.

If we do not deliver what this page lists, or you change your mind before work starts, you get a full refund.

Why buy it from AIGROW

What you can check before you pay, and after the work.

A fixed price
$990, paid once. No subscription, nothing renews. Everything included is listed on this page before you pay.
Proof you can check
Every test runs in your own CI, so you see each run, each failure and its trace yourself. The readme lists each journey, the steps its test takes and what it checks at the end, and the handover links the run in your CI where every test passed.
A public method
The free broken link checker follows the links on up to 50 pages of your site and lists the ones that fail. Run it before you order: it shows the broken links a visitor meets, and the tests here check the forms and journeys behind them. Run the broken link checker

Before you buy

What a journey is, what access we need, where the tests run, what maintenance covers and how to cancel it.

One path a visitor takes from a starting page to a result we can check, such as signing up and landing on the dashboard, searching and seeing results, or sending the contact form and seeing the thank-you message. A checkout from the cart to the order confirmation is one journey.

Any site or web app that runs in a browser, whatever it is built with, if you can give us a staging copy or test accounts. A CAPTCHA has to be off or in its test mode on the site we test. If a journey cannot be tested without a real customer account or a live payment, we tell you before we start, and leave it out or refund you in full.

Read access to the repository where the tests go: the Read role on GitHub or Reporter on GitLab. We work on our own copy and send every change as a pull request (a merge request on GitLab) that you review and merge. A GitHub repository owned by a personal account has no read-only role, so there we push only to our own branches and you merge. We never ask for a password.

No. They run only against your staging site, or against test accounts you give us that hold no real customer data, and payments run only in your provider’s test mode, such as Stripe test mode or the PayPal sandbox. Test logins live in your CI’s secrets, never in the code.

In your own CI, on every deploy, on a schedule, or both, and on your CI minutes. GitHub Actions is free on public repositories; on private ones each plan includes a monthly amount, and use beyond it is billed to the repository owner. The readme says how long a run takes, so you can see what it uses.

For $149 a month we read your test runs every week. When a test fails because of a change you made on purpose, such as a new sign-up form, we update it within 2 working days of the failed run or of your note. When it shows a real break, we tell you what broke and where. We also add one new journey a month; an unused journey does not carry over.

Cancel any time from the link in every email we send about it. Maintenance stops at the end of the paid month. The tests and the workflow stay in your repository and keep running in your CI.

No. A test checks the journey it was written for, step by step, and the result at the end. It does not check pages outside those journeys, how fast your site is, how much traffic it takes or how secure it is. We promise the tests, the workflow and the readme, and that every test passed on your staging site at handover.

You do. The tests, the workflow and the readme are in your repository from the day you merge them, and you may change, share or delete them. Playwright is open source, so you need no account with us to keep running them.

The service that fits next

$490

Shop speed fix

We measure four key pages of your Shopify or WooCommerce shop on mobile, fix what slows them on a copy of your theme, and publish when you approve.

See the shop speed fix

Have a real browser walk through your key journeys on every deploy.

Pay once, answer the questionnaire, give us test access, and merge a pull request with up to 8 tested journeys within 10 working days of your answers and access.

Order for $990See every done-for-you service

$990 · paid once · delivered as listed or refunded