
- 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
- Manual Testing
- Integration Testing
- Accessibility Testing
- VAPT
- UI/UX Testing
- Cross-browser Testing
- Usability Testing
- Performance Testing
Azure DevOps
Postman
GitHub
Figma
JMeter
BrowserStack
Axe DevTools
WAVEOWASP ZAP
SonarQube
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.
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.
- 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.
- 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.
- 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.
- 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.
How QAonTOP tested Supply Ontario
- 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
- 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
- 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
- 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
- 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
The engagement in numbers
Full-stack QA engineers embedded in Azure DevOps sprints
Test cases across websites, PWA, APIs and integrations
Official languages tested on every release
Accessibility issues found and verified fixed
Critical or high vulnerabilities open at release
Browser and device combinations on BrowserStack
Before and after the engagement
| Area | Before QAonTOP | With QAonTOP |
|---|---|---|
| Accessibility | Automated 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 quality | French content spot-checked after release. | Paired English and French test cases for pages, forms, errors and notifications, run before every release. |
| Integrations | Integration issues found late, during user acceptance testing or in production. | API and database checks every sprint, so broken hand-offs are caught before UAT. |
| Security | Point-in-time security reviews with long gaps between them. | OWASP ZAP scans, manual VAPT and SonarQube quality gates built into the release cycle. |
| Performance | Load behaviour unknown ahead of high-traffic announcements. | JMeter baselines and pre-launch load tests for peak moments such as new calls for vendors. |
| Release evidence | Test evidence scattered across spreadsheets and email. | Test plans, runs and defects linked to user stories in Azure DevOps, giving auditable evidence for every release. |
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.