Submit the form with the screen out of view
Keyboard and screen-reader tests reveal whether errors are discoverable. Follow a failed submission through correction and confirmation instead of checking labels in isolation.
Read articleCobnex blogs / Global
Cobnex blog
AI implementation, software architecture and cloud operations for teams worldwide.
456 articles
Page 8 of 26
Sort the table after selecting a row
Selection, refresh and mobile transitions expose mistakes that static screenshots miss. Test record identity while the visible order changes.
Read articleExpire the session just after the user presses Submit
Test both rejected access and an uncertain write outcome. Recovery must preserve the draft without creating a second business action.
Read articleSearch for the procedure using the words a new starter knows
Relevance failures often begin with vocabulary, outdated content or overbroad synonyms. Test those mechanisms directly instead of relying on exact-title queries.
Read articleTest the dependency path your normal suite never reaches
Focus on the behaviour and privileges introduced by an update. Installation, malformed inputs and fallback code can matter more than the happy-path API call.
Read articleProve that the worker cannot delete its source data
Positive tests establish functionality. Deliberate denial tests establish the boundaries that make a service identity useful.
Read articleHand the incident to someone who did not watch it happen
A rehearsal reveals missing context quickly. Give the incoming responder only the record and ask them to explain the next safe action.
Read articleRestore a backup containing a record you already deleted
Retention testing must include partial failures and recovery. A record disappearing from the live screen is only the first observation.
Read articleCount forbidden passages before scoring relevance
Search quality and access safety answer different questions. Measure both so a useful-looking answer cannot hide a failed permission check.
Read articleSeparate candidate recall from final ranking quality
A missing document and a badly ordered document need different fixes. Measure the retrieval stages separately before changing the model or increasing the context window.
Read articleMeasure correct passages interpreted the wrong way
Retrieval can find the right words and still produce the wrong conclusion. Add interpretation checks for the context that document splitting can remove.
Read articleScore claim support separately from polished writing
A fluent answer can still misstate its evidence. Measure whether its claims are supported, whether important conditions survived and whether readers can inspect the source.
Read articleMeasure freshness from the business change
A healthy ingestion job can coexist with stale answers. Measure the interval a reader experiences, then use pipeline timings to explain it.
Read articleDistinguish suspicious output from a successful attack
An assistant can repeat hostile text without executing it, or claim to refuse while a tool still runs. Security results need observable application outcomes.
Read articleCount attempted actions as well as completed tasks
Task completion does not show how much unnecessary or prohibited work an agent tried along the way. Measure the action path as well as the final result.
Read articleMeasure approvals that actually change the outcome
A high approval rate does not show that review is useful. Look at corrections, missed errors and the time people need to understand a proposal.
Read articleMeasure recovery by the final business state
A restarted worker is not a recovered task until its effects are correct and its status is understandable. Measure duplication, unresolved work and operator effort together.
Read articleAn average score can hide the expensive failure
Keep task coverage and failure consequence visible. A candidate that improves easy answers while mishandling a critical exception may be a worse release.
Read article