Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Testing & Quality Architecture”
Quality Attribute Scenario
A structured, testable statement of a non-functional requirement: source, stimulus, environment, artefact, response, response measure.
LLM Evaluation
A repeatable measurement of whether an AI system's outputs are good enough, on cases that reflect the actual task.
Test Pyramid
A distribution of tests weighted towards many fast unit tests, fewer integration tests, and very few slow end-to-end tests.
Test Strategy Altitude
Deciding which risks are verified at which level, so that each layer tests something the layers below it structurally cannot.
Architecture Trade-off Analysis Method
A structured evaluation that scores an architecture against prioritised quality-attribute scenarios and identifies the points where those attributes conflict.
Booking.com's Experimentation Platform
Booking.com runs over a thousand concurrent experiments and treats the ability to test any change safely as a platform capability rather than a product feature.
Delivery vs Maintainability
Choosing where to take deliberate shortcuts, based on which kinds of debt are cheap to repay and which compound.
Fitness Function
An automated check that an architectural characteristic still holds, run continuously rather than reviewed occasionally.
Non-Functional Requirement
A requirement about how well the system must behave rather than what it must do — latency, availability, throughput, security, cost.
Time to Market
How long it takes to get a capability in front of customers — often the constraint that dominates every other architectural quality.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Architecture Decision Log
The ordered, immutable collection of a system's decision records, read as a history rather than as a specification.
Architecture Decision Record
A short, immutable document capturing one architectural decision, its context, the alternatives, and its consequences.
A client wants an assistant that answers questions from 50,000 internal documents which change weekly. RAG or fine-tuning? What actually determines the quality?
What the interviewer is testing Whether you understand what each technique actually does, and whether you know that RAG quality is a retrieval problem. Why RAG
You are starting a greenfield platform. How do you establish what the architecture must satisfy before designing anything?
Separate three different things first Requirements can be traded against one another. Constraints cannot — a design violating one is not a trade off but a failu
Six weeks before launch, an accessibility audit returns 200 issues. The team's automated checks were green. Why, and what do you do?
Why the checks were green Automated tooling reliably decides roughly a third of the criteria: missing alternative text, insufficient contrast, absent form label
You need to ship a rewrite of the pricing engine. Same inputs, same expected outputs, completely new implementation. How do you release it?
What the interviewer is testing Whether you know that release strategy is part of architecture, and whether you reach for verification techniques beyond "test i
Your test quarantine has grown to 140 tests over a year. What has gone wrong and how do you recover?
What went wrong Quarantine without a cap and without a deadline becomes a graveyard. Each individual decision was reasonable — move the flaky test aside, raise
A CFO asks why the architecture function should be funded when it ships no features. You have five minutes. What do you say?
Do not answer with activities "We produce standards, run a review board and maintain the technology radar" describes what the function does, not what the busine
A regulator asks how you ensure marketing consent withdrawal is honoured everywhere. What does the architecture need to show?
The answer they want is mechanism plus evidence Not "we have a consent database". They want to see how a withdrawal reaches every system that could act on it, a
A serverless API works in testing and fails under load with connection errors. The database is at 5% CPU. Explain and fix.
The mechanism Serverless functions scale by creating independent execution environments , each with its own process and its own connection pool. Two hundred con
Testing & Quality Architecture
General material on designing a testing strategy as an architectural concern.
Accessibility Testing
Automated checks, their ceiling, and the manual testing that has to sit above it.
Contract Testing at Scale
Keeping dozens of services compatible without an environment that runs all of them.
Mutation Testing
Measuring whether tests would actually notice a defect, not just cover a line.
Quality Gates
Thresholds that block a release, who may override them, and how they decay.
Security Testing in the Pipeline
SAST, DAST, dependency and secret scanning, and what to do with the findings.
Test Architecture Strategy
Choosing what to verify where, given the failure modes that actually occur.
Testing in Production
Synthetic transactions, dark launches and shadow traffic, done deliberately and safely.
Chaos as a Test
Fault injection with a hypothesis, a blast radius and an abort condition.
Consumer-Driven Contracts
Consumers declaring what they rely on, and providers verifying against those declarations.
End-to-End Test Economics
Why broad end-to-end suites get slow, flaky and abandoned, and what to keep.
Environment Parity
The differences between staging and production that decide which bugs survive to release.
Flaky Test Management
Quarantine, detection, and the trust a suite loses once red stops meaning broken.
Integration Test Boundaries
What sits inside a test's boundary, what is faked, and the confidence that follows.
Non-Functional Test Strategy
Testing availability, latency, security and recovery rather than only behaviour.
Performance Test Design
Workload models, warm-up, think time, and the distribution the average hides.
Service Virtualisation
Standing in for a dependency you cannot call, and keeping the stand-in honest.
Synthetic Data
Generating data with the shape and edge cases of the real thing, and where it misleads.
Test Data Management
Realistic data without copying production personal data into a weaker environment.
Test Pyramid Shapes
Pyramid, trophy and honeycomb, and the system properties that justify each shape.
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
Quality Attributes
Availability, latency, throughput, security, cost — expressed as testable scenarios.
Testing Strategies
The pyramid, and the contract tests distributed systems add to it.
Chunking & Retrieval
Structure-aware splitting, hybrid search and why chunking dominates quality.
Data Governance
Ownership, lineage, quality, catalogues and who may see what.
Functional vs Non-Functional
Behaviour versus quality of behaviour, and why only the second constrains structure.
AI-Era Architecture
General material on architecting systems that include models.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Architecture Communication
General material on communicating architecture.
Architecture Compliance Checks
Automating conformance to standards so review effort goes to the genuinely novel.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Testing & Quality Architecture
Deciding what evidence says a change is safe, at what cost, and at which layer.
Regulatory & Data Protection Architecture
The obligations that constrain a design before a single quality attribute is discussed.
AI-Era Architecture
AI workloads meeting security, data, networking, reliability and cost.
API & Integration Architecture
Contracts between systems, and the compatibility discipline that keeps them working.
Architecture Communication
Explain the same architecture to a CEO, an engineering manager and an engineer.