Public Sector QA Case Study: Supply Ontario | QAonTOP Skip to main content
QAonTOP
Contact Us
Case studySupply Chain Management

Supply Ontario

Accessible, secure and bilingual: QA for Ontario’s public-sector procurement platforms

Supply Ontario is the provincial Crown agency centralizing supply chain management and procurement for Ontario’s public sector. Four QAonTOP engineers test the digital services that buyers, vendors and the public rely on.

Supply Ontario

Public-sector procurement, tested in both languages.

Bilingual EN / FRAccessibleSecure
✓Register
✓Source
✓Bid
✓Evaluate
✓Award
Ontario public sector · Buyers & vendorsQA by QAonTOP
1,800+

Test cases across websites, PWA, APIs and integrations

400+

Accessibility issues found and verified fixed

0

Critical or high vulnerabilities open at release

30+

Browser and device combinations on BrowserStack

Client
Supply Ontario
Industry
Public sector · Supply chain & procurement
Engagement
Ongoing · 1.6+ years
QA team
4 full-stack QA engineers
Platforms
Websites · Mobile Web · PWA · API · Azure Cloud · Database
Services
  • Manual Testing
  • Integration Testing
  • Accessibility Testing
  • VAPT
  • UI/UX Testing
  • Cross-browser Testing
  • Usability Testing
  • Performance Testing
Tools
  • Azure DevOps
  • Postman
  • GitHub
  • Figma
  • JMeter
  • BrowserStack
  • Axe DevTools
  • WAVE
  • OWASP ZAP
  • SonarQube
01Overview

About the project

Supply Ontario is a provincial Crown agency of the Government of Ontario, established in 2020 to centralize and modernize supply chain management and public-sector procurement. It serves ministries, provincial agencies, hospitals, school boards and other broader-public-sector organizations, and manages enterprise-wide Vendor of Record arrangements, strategic inventory and Buy Ontario procurement directives.

Its digital estate spans a bilingual public website, buyer and vendor-facing services, procurement bulletins, training content and integrations running on Azure. Every one of these has to meet Ontario’s accessibility obligations, protect vendor and procurement data, and work equally well in English and French.

QAonTOP has supported Supply Ontario for more than 1.6 years with four full-stack QA engineers working inside Azure DevOps sprints, covering functional, integration, accessibility, security, usability and performance testing.

02The challenge

What made this hard

Public-sector software is judged on more than whether it works. It has to be accessible to every Ontarian, secure enough for procurement data, identical in both official languages and dependable when a major call for vendors goes live.

  1. CHALLENGE 01

    Accessibility is a legal duty

    Under the AODA, public-facing Ontario websites must meet WCAG 2.0 Level AA. Automated scanners catch only part of that; keyboard, screen-reader and content issues need human testing.

  2. CHALLENGE 02

    Two official languages, one experience

    Every page, form, error message and email exists in English and French. Missing translations, truncated labels and mismatched links are easy to ship and hard to spot.

  3. CHALLENGE 03

    Many systems, one journey

    Buyer and vendor journeys pass through web front ends, APIs, Azure services and databases. A break in one integration surfaces as a confusing failure somewhere else.

  4. CHALLENGE 04

    Procurement data must stay protected

    Vendor registrations, submissions and pricing are sensitive. Security had to be verified continuously, not audited once a year.

03Our approach

How QAonTOP tested Supply Ontario

  1. 01

    Embed in Azure DevOps

    Joined sprint ceremonies, linked test plans and cases to user stories in Azure DevOps, and agreed a Definition of Done that includes accessibility, bilingual and security checks — not just functional sign-off.

    Tools  Azure DevOps · GitHub

  2. 02

    Review designs before build

    Checked Figma designs for colour contrast, focus order, heading structure and French text expansion before development started, so fewer accessibility and layout defects reached code.

    Tools  Figma · Axe DevTools

  3. 03

    Test the integrations end to end

    Postman collections validate the APIs between front ends, Azure services and databases, with database checks confirming that what a vendor submits is what gets stored and shown to buyers.

    Tools  Postman · Azure DevOps

  4. 04

    Accessibility by tool and by hand

    Axe DevTools and WAVE scans on every release, followed by manual keyboard-only and screen-reader passes in both languages against WCAG AA success criteria.

    Tools  Axe DevTools · WAVE

  5. 05

    Security and performance before release

    OWASP ZAP scans and manual VAPT against the OWASP Top 10, SonarQube quality gates in the pipeline, JMeter load tests ahead of major announcements, and BrowserStack coverage across browsers and devices.

    Tools  OWASP ZAP · SonarQube · JMeter · BrowserStack

04Results

The engagement in numbers

4

Full-stack QA engineers embedded in Azure DevOps sprints

1,800+

Test cases across websites, PWA, APIs and integrations

2

Official languages tested on every release

400+

Accessibility issues found and verified fixed

0

Critical or high vulnerabilities open at release

30+

Browser and device combinations on BrowserStack

05Impact of QAonTOP

Before and after the engagement

AreaBefore QAonTOPWith QAonTOP
AccessibilityAutomated scans run occasionally; manual screen-reader testing was rare.Axe and WAVE on every release plus manual keyboard and screen-reader passes in English and French, tracked against WCAG AA.
Bilingual qualityFrench content spot-checked after release.Paired English and French test cases for pages, forms, errors and notifications, run before every release.
IntegrationsIntegration issues found late, during user acceptance testing or in production.API and database checks every sprint, so broken hand-offs are caught before UAT.
SecurityPoint-in-time security reviews with long gaps between them.OWASP ZAP scans, manual VAPT and SonarQube quality gates built into the release cycle.
PerformanceLoad behaviour unknown ahead of high-traffic announcements.JMeter baselines and pre-launch load tests for peak moments such as new calls for vendors.
Release evidenceTest evidence scattered across spreadsheets and email.Test plans, runs and defects linked to user stories in Azure DevOps, giving auditable evidence for every release.
06Services delivered

What we covered

Manual Testing

Functional coverage of public pages, buyer and vendor journeys, forms and content workflows.

Integration Testing

Postman and database checks across front ends, APIs, Azure services and data stores.

Accessibility Testing

WCAG AA audits with Axe DevTools and WAVE, plus manual keyboard and screen-reader testing in both languages.

VAPT

OWASP ZAP scanning and manual penetration testing against the OWASP Top 10, backed by SonarQube code analysis.

UI/UX Testing

Design-to-build checks against Figma for layout, states, contrast and French text expansion.

Cross-browser Testing

BrowserStack runs across desktop and mobile browsers, including PWA behaviour on real devices.

Usability Testing

Task-based walkthroughs of buyer and vendor journeys, with findings prioritised with the product team.

Performance Testing

JMeter load and spike tests on key pages and APIs ahead of high-traffic announcements.

Planning a similar project?

Get a ballpark QA cost in under two minutes.

Choose your platforms, team size and timeline in our cost estimator. No call needed.

See More Case Studies

Your dev team needs a solid QA partner

Free one-week POCNDA before accessA QA lead replies the same working day