Skip to main content
DevTools
Quality Telemetry Platform

Thirteen frameworks. One verdict: ship or don't.

A 13-framework testing infrastructure covering unit, E2E, mobile, security, BDD, performance, contract, visual regression, and Lighthouse CI.

13
Frameworks
< 8 min
CI Run Time
0
Prod Regressions Missed
90+
Lighthouse Score
Problem

The challenge

A test suite that only covers the happy path isn't a safety net — it's a false sense of security. Real quality engineering means having the right kind of test at every layer: contracts that prevent API breakage, visual regression that catches layout drift, performance budgets that catch bundle bloat, security scans that flag injection vectors before they hit production.

The Quality Telemetry Platform is the testing infrastructure that runs under all Sage Ideas products. It's not a project delivered to a client — it's the engineering discipline that makes every client engagement trustworthy.

The challenge: building a coherent, maintainable multi-framework testing system that doesn't collapse under its own weight. The risk with "13 frameworks" is that it becomes an unmaintained museum. The architecture here is designed so each framework has a single, non-overlapping responsibility.

Approach

How we built it

Framework responsibility map: Jest (unit — pure functions, utilities), Vitest (fast unit tests for Next.js components), Playwright (E2E browser tests — user flows, auth), Testing Library (component integration), Supertest (API endpoint contract), Pact (consumer/provider contract tests), Cypress (supplemental E2E for visual-heavy flows).

k6 (performance/load — response time under traffic), Lighthouse CI (performance budgets — CWV, accessibility, SEO), OWASP ZAP (DAST security scan — injection, XSS, misconfiguration), Axe (WCAG 2.1 AA automated audit), Percy/Chromatic (visual regression — pixel-diff for UI components), Cucumber/BDD (behavior specs — readable test scenarios).

The architecture principle: each framework owns a layer. Tests don't duplicate each other's coverage. If a bug can be caught by a unit test, it never reaches the E2E layer. This makes the suite fast, focused, and maintainable.

Build

What shipped

13 configured, actively maintained framework integrations. GitHub Actions CI pipeline running all frameworks in parallel with appropriate test gates. Lighthouse CI budget configuration (LCP < 2.5s, CLS < 0.1, TBT < 200ms).

Playwright E2E suite covering authentication, checkout, and core user flows across all products. OWASP ZAP automated security scan on every production deployment. Pact contract tests for all cross-service API boundaries. Percy visual regression baseline for all critical UI components.

Reporting: test results aggregated into GitHub PR checks and Slack notifications.

Outcome

Results

Zero production regressions caught in post-deploy monitoring that weren't first caught by CI (across 12 months of active use). Lighthouse CI budgets maintained: all Sage Ideas products score 90+ on Performance and Accessibility.

Contract testing layer prevented 3 breaking API changes from reaching production during Nexural development. Full test suite runs in under 8 minutes in CI (parallelized across 4 runners).

Testing infrastructure is a product decision, not a technical nicety. The studio now starts every new engagement with this infrastructure in place — not as an upgrade, but as the foundation.

Artifacts

Available

  • GitHub: Testing framework configuration templates
  • CI pipeline configuration
  • Lighthouse CI budget documentation
  • Test coverage policy documentation