Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Non-Functional Test Strategy”
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.
Non-Functional Requirement
A requirement about how well the system must behave rather than what it must do — latency, availability, throughput, security, cost.
Test Strategy Altitude
Deciding which risks are verified at which level, so that each layer tests something the layers below it structurally cannot.
Cross-Functional Requirement
A quality the system must exhibit across its features rather than a behaviour it must perform, so named because it cuts across all functionality.
Quality Attribute Scenario
A structured, testable statement of a non-functional requirement: source, stimulus, environment, artefact, response, response measure.
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.
Attribute History Strategy
The per-attribute decision about whether history is overwritten, versioned or kept alongside the current value, which is a business question rather than a technical one.
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.
Boundary Volatility Test
Evaluating a proposed service boundary by asking whether the things on either side change for different reasons and at different rates.
Caching Strategy
The chosen pattern for how a cache is populated, read and invalidated — cache-aside, read-through, write-through or write-behind.
Chunk Boundary Strategy
How source documents are split for embedding, which determines whether retrieved passages are self-contained and coherent.
Control Test Automation
Executing a control's test continuously against the whole population rather than sampling it annually, which changes both the detection latency and the strength of the evidence.
Database Migration Strategy
The approach for moving data to a new store, which is usually the longest pole and the highest risk in any modernisation.
Differentiation Test
The question of whether a capability is a source of competitive advantage, used as the primary filter in build-versus-buy decisions.
End-to-End Test Cost Curve
How the cost of a broad end-to-end suite grows with its size while its marginal value falls, and where the two cross.
Fallback Strategy
What a caller does instead when a circuit breaker is open — the part of the pattern that determines whether failing fast helps anyone.
Functional Cohesion
The strongest form of cohesion, in which every element of a module contributes to a single well-defined task.
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.
Refactoring Under Test
Changing internal structure without changing behaviour, with tests as the mechanism that makes the claim verifiable.
Soak Test
Running sustained realistic load for hours or days to expose defects that accumulate over time rather than appearing under peak load.
Stress Test
Driving load beyond expected capacity to observe how the system behaves at and past its breaking point.
Subject Naming Strategy
How schemas are keyed in a registry — per topic, per record type, or both — which determines whether one topic may carry several event types.
Tagging Strategy
A defined, enforced set of metadata labels applied to every resource, without which cost allocation, ownership and lifecycle automation are all impossible.
Test Data Provisioning
Getting each test the data it needs, in a state it can rely on, without copying production personal data into a weaker environment.
Test Double Boundary
The line inside a test between what is real and what is substituted, which determines exactly what the test can and cannot prove.
Test Pyramid
A distribution of tests weighted towards many fast unit tests, fewer integration tests, and very few slow end-to-end tests.
Test Quarantine
Moving an intermittently failing test out of the blocking suite into a tracked, owned backlog, so a red build keeps meaning something.
Testing Strategy Shape
The distribution of tests across levels, chosen so that feedback is fast where it can be and confidence is real where it must be.
Alert Fatigue
The desensitisation that follows from alerts that are frequent, non-actionable, or not tied to user impact — after which real alerts are missed too.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Arrival Rate Model
Driving a load test by requests arriving per second regardless of how the system responds, rather than by a fixed number of virtual users.
Assumption Excavation
Deliberately surfacing the unstated beliefs behind a design or a requirement, to test which are constraints and which are merely habits.
Base Image Currency
How far behind the fleet's running images are from their patched base, which is the number that decides how fast a critical vulnerability can be closed.
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.
A project is three sprints from launch and no non-functional requirements were ever written down. What do you do?
Do not write a full NFR matrix now There is no time, and most of the design decisions those numbers would have constrained have already been made. Writing twelv
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
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 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",
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
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
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.
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 new platform must serve a public partner API, three internal front-ends with different data needs, and high-volume service-to-service traffic. Choose the API styles and defend the choice.
Resist "pick one" These are three different problems with three different consumers. Standardising on one style optimises for architectural tidiness at the expe
A team's CI suite fails roughly one run in three for reasons unrelated to the change. Everyone reruns until green. How do you recover the situation?
Recognise what has actually been lost The suite is no longer a gate. Once the team's reflex on red is "rerun", that reflex is applied to genuine failures too, a
Non-Functional Test Strategy
Testing availability, latency, security and recovery rather than only behaviour.
Functional vs Non-Functional
Behaviour versus quality of behaviour, and why only the second constrains structure.
Test Architecture Strategy
Choosing what to verify where, given the failure modes that actually occur.
Chaos as a Test
Fault injection with a hypothesis, a blast radius and an abort condition.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
End-to-End Test Economics
Why broad end-to-end suites get slow, flaky and abandoned, and what to keep.
Environment Strategy
How many environments earn their cost, what each proves, and what none of them prove.
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.
Mobile Release Strategy
Store review, staged rollout, and supporting versions you can never force off.
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.
UI Monorepo Strategy
One repository for many front ends, and the build graph that makes it viable.