Test planning
Select routes, workflows, browsers, devices, and data conditions that represent the release risk.
Check the website against the journeys it needs to support.
Norml tests website functionality, responsive layouts, content, and integrations before or after a release, with reproducible findings and verification of fixes.
Book a callA launch checklist should cover how people use the website.
A new release changes important pages or forms.
The website needs review across agreed browsers and screen sizes.
Connected tools must receive the expected data.
Developers need precise bug reports and a clear retest record.
What our website quality assurance services include.
We define the test scope around the website requirements and critical journeys. Findings include the conditions, steps, observed behavior, and expected result so the team can reproduce and resolve them.
Functional testing
Exercise navigation, forms, validation, account actions, and connected services included in the scope.
Layout and content review
Check responsive behavior, text, assets, links, and visual consistency against the approved requirements.
Issue triage and retesting
Record reproducible bugs, clarify priority, and verify corrections in the appropriate environment.
Website quality assurance deliverables.
The agreed scope identifies which of these deliverables your project needs.
- 01
A scoped test plan.
- 02
Completed test evidence.
- 03
Reproducible bug reports.
- 04
A retest record for fixes.
- 05
A release-readiness summary with open issues.
Our process
How our website quality assurance process works.
Agree coverage
Identify critical workflows and define the acceptance checks for the release.
[ 01 ]
Run the checks
Test the agreed combinations and record failures with evidence.
[ 02 ]
Review findings
Help the delivery team understand each issue and its effect on the user task.
[ 03 ]
Verify corrections
Retest fixes and document the final status of unresolved items.
[ 04 ]Website quality assurance questions.
Does QA include fixing the bugs?
Testing and implementation responsibilities are agreed separately. Norml can handle both when the scope includes development.
Can you test a site built by another team?
Yes. We need the requirements, environment access, and any accounts required for the selected journeys.
Does a pass guarantee there are no bugs?
No. It means the agreed checks passed under the recorded conditions. Untested scenarios remain outside that conclusion.
Can this continue after launch?
Yes. Recurring checks can be organized around critical workflows and planned website updates.
See how this work fits into our website maintenance service.