Skip to content
TREN
Start a project

Test automation

Every change gets the important paths of your site tried automatically, so bugs are caught before customers see them.

Typical targets; the real figure is measured in the pilot.

  • 90%+Coverage target, for the critical flows we select
  • On every changeTests run automatically
  • Within minutesTarget for a failure report being ready

The problem

You make a small change and later find the checkout or a form is broken. Clicking through the site by hand on every update takes time and you still miss things. Often you hear about the bug when a customer writes in.

Who it is for

  • E-commerce and order-taking sites
  • Software teams that update often
  • Businesses that collect leads through forms
  • Anyone who cares about speed and Google scores

What it does

  1. End-to-end tests

    Playwright walks the site like a real user: home page, form, cart, checkout.

  2. API tests

    Background services are checked separately to confirm they answer correctly.

  3. Runs on every change

    With GitHub Actions, tests run on their own each time the code changes.

  4. Proof of failure

    When a test breaks, a screenshot and a video are ready in the report.

  5. Speed tracking

    Core Web Vitals are watched and you get an alert if a page slows down.

  6. Load testing

    With k6 we try how the site behaves when many visitors arrive at once.

How we deliver it

  1. 01

    We pick the critical paths

    We identify the flows that bring money or customers: form, order, login, booking.

  2. 02

    We write the tests

    We write tests for these flows and decide together what you should see when one fails.

  3. 03

    We wire it to run itself

    We connect the tests to GitHub Actions. They run on every change and tell you or your team the result.

  4. 04

    We report and maintain

    We show results in a plain report and keep the tests current as the site changes.

Works with

  • Playwright
  • GitHub Actions
  • k6
  • Lighthouse
  • Core Web Vitals

Questions

My site was built by someone else. Does that matter?

No. The tests try the site from the outside like a visitor. It doesn't matter who owns the code; we only need access to the site and, if needed, a test account.

How long does setup take?

For a few critical flows, a first version usually takes 1-2 weeks. Bigger scope takes longer.

Can the tests mess up real orders?

No. We run tests on a staging environment or with a test account, and we don't touch real customer data.

Can I set it up once and forget it?

Tests need updating as the site changes. If you like, we keep them current as part of monthly maintenance.

More from this service

Software

Test automation

Ask for a free analysis