Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Test Architecture Strategy”
Test Strategy Altitude
Deciding which risks are verified at which level, so that each layer tests something the layers below it structurally cannot.
Testability as a Design Property
How cheaply a system's behaviour can be observed and controlled, which is decided by architecture and largely fixed before any test is written.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Backup Strategy
A plan for what is copied, how often, where to, how long it is kept, and — the part that decides whether it is real — how the restore is verified.
Indexing Strategy
Choosing the set of indexes a table carries by working backwards from its actual queries, and accepting the write cost that each one adds.
Test Pyramid
A distribution of tests weighted towards many fast unit tests, fewer integration tests, and very few slow end-to-end tests.
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.
Business Capability
What a business does, expressed stably and independently of how it currently does it or who is responsible.
Capability Map
A structured view of everything a business does, used as the stable frame for mapping applications, investment, ownership and gaps.
Multi-Cloud
Deliberately running across more than one cloud provider — a decision with a much higher cost than the lock-in it is usually adopted to avoid.
Non-Functional Acceptance
Treating quality-attribute targets as acceptance criteria with automated verification, so a release can fail on latency the way it fails on a broken feature.
Query Plan
The database's chosen strategy for executing a query, and the first thing to look at when one is slow.
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.
Architecture Development Method
TOGAF's iterative cycle for developing enterprise architecture, which is valuable as a checklist of concerns and harmful when followed literally.
Architecture Principle
A durable, agreed rule that constrains design decisions in advance, stated with its rationale and its implications.
Netflix built its own CDN; Dropbox moved storage off S3. Both are usually wrong. What conditions made them right, and how do you test for those conditions?
What the interviewer is testing Whether you can extract the conditions from a famous decision rather than the decision itself. These two cases are the most comm
Six teams share one integration test environment. Bookings are made a week ahead and releases slip when someone overruns. How do you fix it?
Name the cost first The queue is not an inconvenience; it is lead time. Measure it: for the last twenty changes, how many days elapsed between "ready to test" a
When should a service call another synchronously, and when should it publish an event instead? Give me the deciding test, not a preference.
The deciding test Does this user action succeed or fail based on this callee's response? If yes, the call is synchronous, because you need the answer to decide.
An end-to-end suite of 340 tests takes four hours and fails spuriously about half the time. The team wants to parallelise it. Is that the right move?
Parallelising treats the symptom It might halve the runtime. It will not touch the flakiness — in fact parallelisation often worsens it, by exposing shared stat
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 DR test fails: the secondary region cannot launch enough instances. What happened, and what standing checks prevent it?
What happened Service quotas in the secondary region are far lower than in the primary , because nothing has ever run there at scale. Quotas are per account and
A platform of 40 services has logs only, and incidents take hours to diagnose. Design the observability strategy and its rollout order.
Why logs alone fail at this size Logs answer "what happened in this service". They cannot answer "where did this request spend its time across twelve services",
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
An executive says "we need an AI strategy" and asks you to come back in two weeks. How do you handle the ambiguity?
Do not go away and produce a strategy document A document answering a question nobody has articulated will be received politely and shelved. The brief is ambigu
Test Architecture Strategy
Choosing what to verify where, given the failure modes that actually occur.
Non-Functional Test Strategy
Testing availability, latency, security and recovery rather than only behaviour.
Chaos as a Test
Fault injection with a hypothesis, a blast radius and an abort condition.
End-to-End Test Economics
Why broad end-to-end suites get slow, flaky and abandoned, and what to keep.
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.
Performance Test Design
Workload models, warm-up, think time, and the distribution the average hides.
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.
Testing & Quality Architecture
General material on designing a testing strategy as an architectural concern.
UI Monorepo Strategy
One repository for many front ends, and the build graph that makes it viable.
Enterprise Integration
Estate-wide integration strategy, standards and shared infrastructure.
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.
Architecture Decision-Making
General material on making and recording architectural decisions.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Architecture Documentation
What to write down, at what altitude, and what nobody will ever read.
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Patterns
General material on architectural patterns and their trade-offs.
Architecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
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.
Architecture Decision-Making
Where senior engineer becomes architect: evaluate, choose, write it down.
Architecture Fundamentals
What architecture actually is: drivers, constraints, trade-offs and the principles behind them.
Architecture Patterns
Patterns as tools for recurring problems, with forces and consequences.