Test the table that continues on the next page
Multi-page tables expose mistakes that ordinary paragraph tests miss. Check the relationship between a value, its column heading and the note that qualifies it.
Read articleAI implementation, software architecture and cloud operations for teams worldwide.
456 articles
Page 6 of 26
Multi-page tables expose mistakes that ordinary paragraph tests miss. Check the relationship between a value, its column heading and the note that qualifies it.
Read articleA useful citation test uses a relevant source and a subtly wrong answer. This exposes failures that broken-link checks cannot find.
Read articleTest withdrawal after the system has created passages, caches and conversation history. An empty search result alone does not prove removal is complete.
Read articleExercise the document-to-tool boundary with a synthetic file and a harmless test destination. Measure what the application does, not only what the assistant says.
Read articleThe hardest retry case is a successful mutation whose response never reaches the agent. Inject that failure deliberately and inspect the business record.
Read articleA small payload mutation is enough to test whether approval is bound to the action. Use a material field and verify that execution cannot reuse the earlier decision.
Read articleRecovery tests need precise fault locations. Stopping a process at a random time rarely proves how it handles the gap between an external effect and its local record.
Read articleNear-duplicate cases can make an evaluation look independent when it is testing familiar material. Inspect relationships between examples, not just identical strings.
Read articleSchema checks will accept many semantically wrong values. Test a document where nearby fields are easy to confuse and assert the business meaning of each output.
Read articleError paths often log more than successful requests. Use a synthetic marker to find diagnostic copies and unexpected fallbacks without exposing real information.
Read articleA lower initial request cost can disappear through repair loops. Test a persistent validation failure and verify that the task stops within its total allowance.
Read articleA model may know a plausible answer from general knowledge while the product requires approved evidence. Test that distinction with a question just outside the source collection.
Read articleTest the paths most likely to avoid the public contract: direct repository imports, background jobs and administrative updates. The same invariant should hold for each supported caller.
Read articleThe outbox's duplicate window is predictable. Stop the worker after broker acceptance and verify that replay does not repeat the consumer's business effect.
Read articleSequential retries can pass while concurrent requests still duplicate an effect. Use a barrier to make two callers compete for the same operation identity.
Read articleError contracts influence retries, forms and recovery. Test them with supported older clients, not only with a server-side schema validator.
Read articleA recovery path that only works when every corrective call succeeds is incomplete. Test the state left behind when compensation is rejected or its response is lost.
Read articleSimilar records expose missing scope in queries and caches. Use two isolated test tenants and exercise the same operation through every supported path.
Read article