Topic
Software testing and QA
Good testing is layered: unit and API tests close to the code, end-to-end tests on the journeys that matter, and automated accessibility and regression checks in the pipeline. Our pods include a QA lead, and we ship our own API testing product.
Case studies
All case studiesWhere it has shipped
Essays
All essaysRead more on this
Engineering Practice8 min read
API testing explained: types, what to automate, and tools
API testing checks an interface directly, below the UI. Learn the five main types, how mocking and test data fit in, and which tests to automate first.
Studio ArchitectureAugust 2026·7 min read
The Techdome Blueprint: how we take a product from a blank repo to production in eight weeks
The five steps of our Blueprint, what each one delivers, how fixed-scope sprints and engineering pods are priced, and how recent builds ran from kickoff to production.
Glossary
Full glossaryTerms explained
- API testingChecking that an API returns the right data and errors for different requests, without going through a user interface.
- Regression testingRe-running tests after a change to confirm that features which worked before still work.
- RustA systems programming language focused on speed and memory safety.
- axe-coreAn open-source engine that tests web pages for accessibility problems automatically, usable in a browser or a CI pipeline.