Book a discovery session

Menu

Services
View all services
Industries
View all industries
Solutions
View all solutions
WorkOffersWho we areTrust CentrePartner with us
Book a discovery session
Explore workBook discovery

Functional and exploratory testing

A working digital service has to do what users need, so we test what it should do and explore what nobody expected it to.

Discuss this capabilityExplore related proof

Problem

01

Scripted tests confirm that software does what the requirements say. They rarely find the problems users hit: the unusual input, the interrupted journey, the screen reader that announces the wrong thing.

Outcomes

  • Requirements tested against clear acceptance criteria.
  • Problems found by skilled exploration, beyond the scripted cases.
  • Services checked against WCAG 2.2 AA before launch.
  • Defects reported clearly, with steps to reproduce.
  • A confident release decision based on evidence.

Scope

In scope

  • Test analysis from requirements and user stories.
  • Scripted functional testing.
  • Exploratory testing sessions.
  • Regression testing before release.
  • Defect reporting and triage support.

Not included

  • Fixing the defects. Developers fix them; we retest.

Accessibility testing

Accessibility affects whether people can use a service at all. We test services and content against WCAG 2.2 AA using automated scans, keyboard-only use, zoom and reflow checks, and a representative screen-reader pass, then explain each issue in plain terms with how to fix it.

  • Automated and manual WCAG 2.2 AA checks.
  • Keyboard, zoom, reflow and screen-reader testing.
  • Prioritised findings with fix guidance, and retesting.

Approach

  1. Discovery

    We turn requirements into clear, testable acceptance criteria. We agree the riskiest areas and the accessibility standard to test against.

  2. Delivery Planning

    We plan the scripted tests, the exploratory sessions, the accessibility checks, and the browsers and devices to cover.

  3. Build and Test

    We run scripted tests, exploratory sessions and accessibility tests with keyboards, zoom and screen readers. We report defects clearly and retest the fixes. Before go-live, you get the release test summary with known issues stated, and a named person decides whether to go ahead.

  4. Operational Readiness, Hypercare and Closure

    We run regression checks around the release, and check the live service where agreed. We provide extra hypercare for the first few weeks, hand over the test cases and findings to your team, and close the work with your sign-off.

Deliverables

Test analysis and acceptance criteriaTest cases and exploratory session notesDefect reports with steps to reproduceAccessibility findings against WCAG 2.2 AA.Release test summary with known issues stated

Technologies

Test management: Azure DevOps Test Plans or your existing toolAccessibility: automated scanners such as axe, plus NVDA, VoiceOver and keyboard-only testingBrowsers and devices: a matrix agreed against your users

Controls

Every requirement is linked to at least one test.Accessibility testing includes assistive technology as well as automated tools.Test data contains no real personal information unless agreed and protected.Known issues are stated in the release summary.

Frequently Asked Questions

What is exploratory testing?

Testing led by a skilled tester's judgement, rather than a script, to find problems nobody anticipated.

Are automated accessibility tools enough?

No. They find some issues, but keyboard, zoom and screen-reader testing by a person finds many more.

Which accessibility standard do you test against?

WCAG 2.2 at level AA, unless your sector or contract requires something else.

Can you test a service that is already live?

Yes. We often start with an accessibility and functional review of the live service, then prioritise fixes.

Not sure your service works for every user?

A Technical Audit reviews your testing coverage, including accessibility, in 10 to 15 working days and gives you a prioritised remediation plan.

Discuss this capabilityExplore related proof