Phase 1: Discovery, Requirements & Architecture Blueprint
Critical user journeys, environments and flaky existing tests are baselined before any suite is written.
Three pillars. Twelve focused engagements.
DevNord builds maintainable Playwright E2E and API regression suites that run in CI on every change. Characterisation tests protect legacy behaviour, traces make failures obvious, and green builds are the only builds that ship.
This is the service-specific architecture we design and operate. Inspect any node to see its role, the engineering or QA control around it, and how risk is contained.
Tap any node to inspect it.
Hover over a node to inspect it.
Node inspectorSelect any component to see what it does, which control protects it and how we hand it over.
An indicative 12-week cadence for a full engagement. The exact calendar, milestones and price are fixed in your EUR (€) or SEK (kr) proposal after discovery.
Indicative cadence — finalised in your fixed-scope proposal
Critical user journeys, environments and flaky existing tests are baselined before any suite is written.
Page objects, API contract checks and fixtures are built in the first sprints against a stable preview environment.
Manual explorers validate the flows while the new suite runs in CI on every pull request and release candidate.
Traces, reports and SLO-linked alerts are handed over so your team owns a green build as release policy.
Every engagement runs with the same operating model: senior squads, transparent ownership and written evidence at every gate.
Two-week sprint cadence with demoable increments and a written decision log.
Transparent Git repository ownership — repositories land in your organisation from day one.
Infrastructure-as-code (Terraform or Bicep) for every environment, reviewed and reproducible.
Fixed-scope proposals in EUR (€) or SEK (kr), with capped B2B consulting retainers when scope is still emerging.
Bilateral NDA signed before source code, architecture data or credentials are shared.
A Playwright suite is only valuable when it is trusted. DevNord builds resilient tests around stable selectors and explicit fixtures, separates API state setup from UI assertions, and attaches traces to every failure. Flaky tests are quarantined rather than allowed to erode confidence in the gate.
We integrate with GitHub Actions, Azure DevOps or GitLab CI and can target Chromium, Firefox and WebKit across Nordic locales. Proposals are fixed scope in EUR (€) or SEK (kr), with a clearly defined number of journeys and environments.
Every release consumes days of manual clicking, key paths break unnoticed, and old Playwright suites are so flaky that engineers ignore red builds. Testing becomes the reason deployments are rare.
We record real user journeys against the current system, then build resilient Playwright suites using stable locators, isolated data and parallel execution. API contract tests cover integrations, and the whole suite becomes a mandatory CI gate with traces on failure.
Green pipeline means the journey works — not just that the unit tests pass.
Characterisation suites freeze existing behaviour so modernisation cannot silently change it.
Traces, screenshots and request logs make root cause obvious in minutes.
These are service-specific, reviewable assets — not status reports. Your team owns each one.
Still unsure? Write to us at [email protected] — we reply in plain language, without a sales script.
Yes. Playwright drives the browser, not the framework. That makes it ideal for characterising legacy interfaces during modernisation.
We use stable locators, isolated data, explicit waits and parallel-safe fixtures. Flaky tests are quarantined and fixed rather than suppressed.
Not necessarily. We audit what exists, keep reliable parts and replace only the suites that block trust in the gate.
Parallel execution and targeted smoke sets keep feedback fast — typically minutes for PR checks and a fuller overnight regression.
Start with a Blueprint Audit and get a test architecture, journey inventory and CI gate design.