Français
English
Español
Deutsch
NorskPractical guide
Prepare acceptance testing for a website or portal
Turn requirements into test scenarios and make a launch decision supported by evidence.
Practical guide
A case to prepare your project
A request portal gives applicants access to their own cases, agents to assigned cases and supervisors to oversight. Acceptance must test role boundaries as well as form usability.
Illustrative scenario, to adapt to your organisation.Prepare and perform the checks
Define the test data
Prepare test accounts for every role and fictitious cases. Write expected outcomes in advance, including denied access.
Vary conditions
Test keyboard use, mobile screens, limited connectivity, invalid input and expired sessions. Agree a performance threshold for priority journeys.
Organise the decision
Assign defects, distinguish blocking issues from improvements and retest fixes. Rehearse deployment on a representative copy.
A reusable acceptance checklist
Agree thresholds, owners and test data before testing. Retain dated results, exceptions and the acceptance decision.
| Check | Expected result | Evidence to retain |
|---|---|---|
| Access rights | Changing an identifier cannot expose or modify another user’s case. | Role matrix and positive/negative tests. |
| Forms and keyboard | Clear labels, logical focus, understandable errors and recoverable input. | Keyboard walkthrough and user observations. |
| Performance | The essential journey meets the agreed threshold on the reference network and device. | Dated measurements and test conditions. |
| Reversible deployment | Rollback restores service within the agreed data-loss limits. | Rehearsal report and verified backup. |
Decide using evidence
Record the tested version, accepted exceptions, owners and launch conditions. Automated checks complement user observation and a security assessment; they do not replace them.
Standards and reading
References checked on .
Relevant ISO standards
- ISO/IEC 25010:2023
Define measurable product quality criteria.
- ISO/IEC 40500:2025 · WCAG 2.2
Structure web accessibility checks.
These standards help define scope and expected evidence. Citing them does not certify Salott-IT or establish your project’s conformity. A dedicated assessment is required. Include applicable amendments when scoping the engagement.
Technical documentation
Reference books
- The Pragmatic Programmer · 20th Anniversary Edition
David Thomas & Andrew Hunt · Addison-Wesley · 2019
Original synthesis based on official summaries, open documentation and publishers’ public descriptions or contents. Books are selected references, not a universal ranking. Copyrighted book and standards text is not reproduced.
Start with your actual situation.
Scope, responsibilities, timing and acceptance criteria will be defined in the proposal.