Language changes but the profile is lost
From a selected source, the English button opens a default profile. Preserve the public entity parameter, then compare all six destinations. Do not put private notes or drafts in these URLs.
In-depth practical guides
Test from discovery to decision: an acceptance plan connecting navigation, search, language switching, tools, forms and error recovery.
Updated :

AI-generated illustration
A translated page is insufficient if its menu returns to French, search ignores its words or the form produces an unexplained error. Test observable tasks and complete states. This complements text and URL reviews by examining what users can actually accomplish. The following situations are preparation examples, not claimed assignments.
List page families and actions: find a definition, compare sources, open a profile, compose a reference, calculate or make contact. Give each task a starting point, destination and expected result. Include secondary pages, not only primary menu entries.
Include initial state, long content, active filter, no result, invalid input and recovery. Use clearly labelled synthetic data. For contact, separate local validation, safe server rejection and explicitly authorised delivery testing: do not send real messages by default.
Enter through a deep profile and switch language. Check preservation of the entity, filter or selected source where relevant. Inspect lang, direction, labels and messages. Canonicals and hreflang describe equivalent versions; they do not establish that the switcher works.
Write representative queries for each script, with accents, variants and multiple words. Check relevance, result links, pagination and no-result states. A sitemap URL may still be hard to reach through navigation. Test related links and the route back to the section.
Test search, filters, selectors and forms with normal and edge cases. Check expected results, public context, keyboard use, field errors and confirmation. Also test readable content and fallbacks when JavaScript is unavailable.
Record expected and observed results, evidence and severity relative to the task. Fix the shared cause, repeat the failing case and affected languages and components. Passing acceptance means the defined matrix passes; it does not mean every possible use and device has been tested.
After an action, inspect copied text, downloaded files and shared links. Reader-facing explanations should follow the announced language; stable technical keys may remain identical. Compare copied and displayed values and state a source’s reference country. Translating an interface does not change the underlying document’s scope.
Reading workshop
This fictional matrix keeps failures, blockers and unexecuted attempts visible instead of dropping them from the acceptance report.
Fictional data and records for learning: none of these results comes from a live service query.
Six identifiers cover one journey per language here. Their invented states teach follow-up reading; they do not describe checks performed on this website.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| State and count | Affected cases | Fictional observation | Follow-up decision |
|---|---|---|---|
| PASS · 2 cases | FRTOP, ENFORM | The French deep link reaches its section; the English form error remains associated with its field. | Retain expected result, observation and evidence for these two tasks only. |
| FAIL · 1 case | ESSEARCH | A Spanish search result opens a French page despite the Spanish expectation. | Fix language preservation, then rerun the case and related journeys. |
| BLOCKED · 1 case | RULINK | The required destination is unavailable in the demonstration environment. | Identify the missing prerequisite; infer neither success nor a journey defect. |
| NOT_RUN · 2 cases | ARRTL, FIMENU | Arabic bidirectional reading and the Finnish menu have not been tried yet. | Schedule execution; being listed in the matrix is not a result. |
From 1 to 40 cases, without a header: identifier;state. Unique ASCII identifiers of 1–32 characters (letters, digits, dot, hyphen, colon, underscore). Exact states: PASS, FAIL, BLOCKED, NOT_RUN. UTF-8 text, at most 8192 bytes.
This tool defines a completed verdict as PASS or FAIL. BLOCKED remains blocked, possibly after a partial attempt; NOT_RUN was not executed. Success rate uses PASS + FAIL, never only PASS. Without a verdict it remains undefined.
The supplied plan contains failures, blocked or unexecuted cases. Retain these states in the assessment.
| Case | Exact code | Meaning |
|---|---|---|
| FRTOP | PASS | Expected criterion declared satisfied |
| ENFORM | PASS | Expected criterion declared satisfied |
| ESSEARCH | FAIL | Expected criterion declared unsatisfied |
| RULINK | BLOCKED | Blocked attempt without completed verdict |
| ARRTL | NOT_RUN | Unexecuted test |
| FIMENU | NOT_RUN | Unexecuted test |
A declared matrix does not test the site. Scope, evidence, languages and acceptance criteria still need checking. High success among completed cases can coexist with low coverage.
Open each proposition to compare its diagnosis. More checks may still be needed.
Incorrect. The list shows intended scope, not execution or success in each language.
Too quick. That subset omits one blocked and two unexecuted cases; the remaining failure also needs a decision.
That is the complete exercise summary. It retains all six cases and separates an observed defect, a missing prerequisite and outstanding work.
Campaign: DEMO-T06; invented data FRTOP: PASS; expected section reached ENFORM: PASS; error associated with field ESSEARCH: FAIL; wrong-language destination RULINK: BLOCKED; prerequisite unavailable ARRTL: NOT_RUN; visual order and copying to try FIMENU: NOT_RUN; keyboard to try
Identifiers and state codes stay stable; explanations follow the reading language. This log is a demonstration, not the website’s test history.
From a selected source, the English button opens a default profile. Preserve the public entity parameter, then compare all six destinations. Do not put private notes or drafts in these URLs.
An accented query misses an existing profile. Check normalisation and the language index, then multiple words, results and pagination. Equal record counts do not establish relevance.
After rejection the message is off-screen or unassociated with the field. Check localisation, announcement, focus and retention of non-sensitive entries. Retest using a deliberately invalid submission that cannot send a message.
Illustrative case: the form is Spanish but its exported template has French instructions. Open the file using the intended characters and delimiter, then inspect headers, instructions and values. Separate intentionally stable technical identifiers from explanations requiring translation; download completion alone does not validate the journey.
Test example: REF-12/AB appears beside a bracket and number in an Arabic sentence. Check visual order and copied value. Isolate the opposite-direction string with appropriate markup; do not reverse its characters to make one screenshot look correct.
Worked exercise
Fictional example: the values and documents teach the method and do not describe a real organisation.
Testing covers three states per language. Only the initial view was examined, with no data submitted.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Language | Initial | Error | Correction ready |
|---|---|---|---|
| FR | Yes | Not checked | Not checked |
| EN | Yes | Not checked | Not checked |
| ES | Yes | Not checked | Not checked |
| RU | Yes | Not checked | Not checked |
| AR | Yes | Not checked | Not checked |
| FI | Yes | Not checked | Not checked |
There are 6 × 3 = 18 cells; only 6 are covered, one third. The remaining 12 specifically include errors and recovery. Equal numbers of translated pages do not prove translated, usable interactions.
With two planned widths, the matrix becomes 36 cells. Document scope rather than treating two screenshots as general coverage. After correcting a message, replay the error and recovery in the affected language; a screenshot of the initial state does not close that defect. Keep the tested version, announced wording and focus destination so another reviewer can reproduce the result.
Keep matrix, observed state, message, focus and outcome; use an authorised test destination.
Inventory every route and language, then cover each template’s tasks and states. Add targeted checks for unusual profiles and parameters.
Keep useful public context where intended. Avoid placing drafts or sensitive information in URLs; explain when an action resets input.
It detects reproducible regressions. Visual review and keyboard journeys remain necessary to assess readability, understanding and action order.
When the defined criteria pass and remaining defects are explicitly documented. Fix and retest defects blocking the priority task before approval.
They are part of the path and can use different translations or components. A correct page to read does not demonstrate the consistency of the messages displayed after interaction.
DEEPER READING / PRACTICE
A translated page seems correct, but a filter, error or an expected email interrupts the path. A functioning test should perform interactions instead of limiting itself to visual reading.
Updated on .
Testing entry, navigation, search, valid entry, invalid entry and confirmation. Keep the selected language and check the messages effectively presented at each step.
A screenshot does not demonstrate the functioning of an interaction. Shared elements can introduce a regression in several languages after an apparently local correction.
The operation test sheet document cases, expected outcome, obtained outcome and anomaly. The closure requires a new execution of the corrected case and pathways that use the same component.