Video 1: Running the tests
Open on YouTubeA single PowerShell command launches the Playwright test run. It opens a browser and automatically drives the Picasso application by clicking, filling, and navigating through each scenario.
Artifact 1
Muhammad Shaaf Yousaf
Co-op placement at the Ontario Public Service as a .NET Developer
A single PowerShell command launches the Playwright test run. It opens a browser and automatically drives the Picasso application by clicking, filling, and navigating through each scenario.
This Playwright HTML report shows passed and failed tests, the exact step where a failure occurred, and the surrounding trace and context.
Description
As a .NET Developer at the Ontario Public Service, I built an end to end test automation framework for Picasso, an internal platform that hosts several education applications, including the Ontario School Year Calendar, also known as OSYC. The goal was to help QA analysts who are not developers write reliable automated tests without writing code.
I designed the framework using Playwright, TypeScript, and playwright bdd with a strict separation of responsibilities. QA authors only write plain English Gherkin feature files. I implemented the underlying step definitions and reusable action helpers that operate Picasso shared user interface widgets, including buttons, textboxes, dropdowns, multiselects, radio buttons, and checkboxes.
A core design decision was abstracting element selection behind a selectorType parameter. This allows one step sentence to target an element by its accessible role or by any HTML attribute. This kept the shared step library small while making it flexible across every application.
For execution, I wrote a PowerShell orchestration script that retrieves credentials from Azure Key Vault, saves the authenticated browser session, and decodes the JWT expiry claim. The framework can reuse valid sessions and skip unnecessary logins, as shown in Video 1. Test outcomes appear in a detailed Playwright report that pinpoints exactly where a scenario failed, as shown in Video 2.
The framework is now actively used by QA to write regression and smoke suites independently. Through this work, I deepened my skills in Playwright, BDD and Gherkin, TypeScript, Azure Key Vault, JWT handling, and PowerShell.
If I built it again, I would add a searchable step catalogue tool so QA could discover available sentences without reading the documentation.