Skip to content

Pick your style: Denkbaar

Book a conversation

Articles

Knowledge

Every step tested on its own, and deployed automatically with CI/CD

When each step has its own test, you know at once where an error is. CI/CD runs those tests at every change and deploys the result.

A developer views a series of checks on a screen.
Every change goes through building, testing and checking. Illustration: Denkbaar.

An agent writes a lot of code, fast. Then you must also know fast if something is broken, and where. That is why, at Denkbaar, each step has its own test, and a fixed pipeline runs those tests at every change.

Plain technical English Continuous integration (CI) builds and tests the code automatically at every change. Continuous delivery or deployment (CD) puts a tested version live automatically. Playwright is an open source test tool that controls a real browser.

Why it matters

Martin Fowler describes CI as a practice in which everyone merges their changes at least daily, and an automated build with tests verifies each merge. That way you find errors as early as possible. If each step has its own test, a red test points at the step that is broken. Without tests, you search for an error in the whole.

Three parts each have their own coloured square.
A test for each step helps find a fault quickly. Illustration: Denkbaar.

How it works

fails

Change

Pull request

CI: build and all tests

Preview version

Merge

Deploy

Live check

Automatic rollback to the previous version

Each change goes through build and tests, is deployed, and rolls back by itself when the live check fails.

An employee compares two versions of a website.
A failed live check can restore the previous version. Illustration: Denkbaar.

What you do

  1. Test every layer. A unit test per function, a test for how parts work together, and a test that clicks through the browser as a user (for example with Playwright).
  2. Test with real parts. Do not mock what you build or install yourself.
  3. See the test fail first, for the right reason. Then you know it really tests something.
  4. Let CI run everything at every change. On our own site, CI builds all 14 languages; a missing translation makes the test fail.
  5. Keep the fast tests fast, so that you run them locally before every commit.
  6. Deploy with a check and a way back. On our site, the release checks the live site for one minute after the deploy, and restores the previous version by itself when that fails.
  7. Never turn off a test to get green. Fix the cause.

What we can do with you: we set up tests and a CI/CD pipeline for your project, so that every change goes live safely. Book a conversation.

Sources

  1. Martin Fowler: Continuous Integration (2024)
  2. Playwright: Installation and first test (Apache-2.0)

Topics: testingci-cddeploy