Phase 1: Discovery, Requirements & Architecture Blueprint
A risk-based test strategy defines journeys, roles, Nordic locales and acceptance criteria per release.
Three pillars. Twelve focused engagements.
DevNord runs structured exploratory testing, regression charters and user acceptance testing for business-critical B2B systems. We combine senior manual QA with Playwright automation so every release is validated by both human judgement and repeatable gates.
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
A risk-based test strategy defines journeys, roles, Nordic locales and acceptance criteria per release.
Timeboxed exploratory charters run alongside development, with evidence and defects triaged daily.
Managed UAT coordinates participants, scripts and sign-off while Playwright captures the confirmed journeys.
A go / no-go report, defect summary and maintained test-case repository are handed to your product owner.
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.
Automation proves that the system still matches yesterday’s assumptions. Senior manual QA finds the permission edge case, the confusing locale format and the workflow that technically passes but fails for a real user. DevNord runs both: structured exploration and managed UAT first, then codified Playwright regression for the behaviour you accept.
We work in your existing tracker — Jira, Azure DevOps, GitHub Issues or TestRail — and deliver evidence that satisfies Nordic and European audit expectations. Proposals have fixed scope in EUR (€) or SEK (kr) per release train or engagement.
A green pipeline proves the code matches yesterday’s assumptions. It does not find the confusing wizard, the permission edge case or the report that fails only for a Swedish locale. Without senior manual QA and managed UAT, those defects reach the people who pay for the system.
We build a risk-based test strategy, run time-boxed exploratory sessions and manage UAT end to end. Confirmed behaviour is then codified as Playwright E2E and API checks, so the manual insight becomes a permanent regression gate.
Exploratory charters and managed UAT surface usability, data and permission failures while they are still cheap to fix.
Every confirmed journey becomes a traceable test case and a Playwright regression check in your repository.
A written go / no-go report with open defects, severity and sign-off replaces opinion-based launch meetings.
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.
No. DevNord supplies senior manual testing capacity and test leadership. Your product owners and domain experts remain the acceptance authority; we make their job measurable and repeatable.
We publish scripts, collect decisions in a structured tracker, run scheduled sessions and produce a versioned sign-off report that can be audited later.
We adapt to your stack — Jira, Azure DevOps, GitHub Issues, TestRail or Zephyr — and add Playwright for the automated regression layer.
Yes. Test charters explicitly cover locales, date formats, encoding and role-based views, which are common sources of defects in Nordic B2B systems.
Request a fixed-scope proposal in EUR (€) or SEK (kr) for exploratory QA and UAT management on your next release train.