Test specs built from an original six
Coverage the team can keep extending04 defects detectedBUILD FAILED
01/05QA Automation Lead · South Jordan, Utah
Something's broken.Some-thing'sbroken.
I'll find it.
I'm Brayden Pay. I build test automation, lead QA teams, and find the release risks that are easiest to miss.
Focus: Automation · release strategy · team leadership
Watch a real test run ↘Measured in the work
22-month source audit · Sep 2026The numbers point to the same outcome: broader coverage, earlier warnings, and testers who can own the work.
Regressions caught before release in 2026
Issues customers never had to reportGrowth in automated test coverage
More reach without matching headcountQA engineers led, trained, and supported
Independent testers with shared standardsPUBLIC REPOSITORY / 01
Watch the test.
Inspect the code.
The suite separates page behavior, fixtures, and authenticated state so routine UI changes are easier to maintain.
- ArchitecturePage Object Model, custom fixtures, and reusable authenticated sessions.
- CoverageLogin, cart, checkout, full purchase flows, mobile viewports, and REST CRUD.
- CI behaviorEvery push and pull request runs the suite in GitHub Actions; the public badge shows the current result.
How the coverage grew
Repository history · Oct 2025–Sep 2026Automation platformOct 2025 → Sep 2026
Test specsCI workflows
Merged pull requests authored
768 of 972 · Repository auditThe tests get tested, too
74Harness tests protecting the automation platform itselfReliability checks cover the test harness as well as the product.Independent product / Live release
DIGIMORA
A focused number-memory game with 60 progressive levels, custom quick-play sessions, and a clean experience built for light and dark mode.
60 levelsWorks offlineNo ads
Verification stayed part of the build.
I traced a dark-mode failure to SwiftUI environment scope and tested timing races, relaunch persistence, and theme behavior on both platforms. Before release, I also checked signing keys and ignored build artifacts against the remote repository.
The fix came from isolating the cause, not changing colors until something worked.Two releases. One moving plan.
I handled signing, store setup, compliance, and feature parity for both platforms. When Google's device verification blocked one release path, I prepared the listing and remaining launch work in parallel.
Both releases kept moving while store requirements changed.Other systems I've built
Automation · agents · paymentsWorkflow automation
QA Operations Bot
A Slack tool that answers coverage questions, runs live checks, gathers bug context, and routes uncertain results for human review.Ask about this workAgent engineering
Agent Knowledge Layer
Versioned sources, cited references, measured misses, and a critic gate keep AI-assisted QA grounded in evidence.Ask about this workHigh-risk domain testing
Payment Routing QA
Coverage that verifies which processor handled a transaction as well as whether the charge succeeded.Ask about this workWhat I bring to a team
Four ways I contributeAutomation architecture
I separate fixtures, selectors, and suite responsibilities, then add useful failure evidence and tests for the harness itself.
Release judgment
I wire repeatable checks into CI and make failures specific enough for the team to act on.
Risk-based testing
I choose the tool and the test oracle around the risk, from payment routing to native app state.
Team development
I train testers, review their work, and document decisions so coverage does not depend on one person.
How I work
- 01Detect
- 02Isolate
- 03Explain
- 04Verify
- 05Improve
Find it.
Make it useful.
Every report answers four questions: who is affected, how to reproduce it, what the evidence shows, and what must change before release.
For contained, low-risk issues, I use agent-assisted development to trace the cause, prepare a patch, verify the behavior, and open a review-ready pull request.
I've led up to seven QA engineers. Training, work review, and shared decision rules help testers investigate independently and give product and engineering the same evidence.
PlaywrightTypeScriptUI AutomationEnd-to-End TestingRegression TestingExploratory TestingGitHubLinearSlack AutomationVercelMaestroPower Automate
Education
Bachelor of Science, Strategic CommunicationUniversity of Utah · 2023Work history
2020—PresentFluid
QA Automation Lead
Promoted to lead after joining the QA team. I’ve led up to seven QA engineers, trained new testers, assigned their work, and built Playwright coverage around the releases that matter.
Tesla
Data Analyst
Worked through large vehicle datasets, checked questionable records, and brought the problems I found to engineering and operations.
Wasatch Property Management
Financial Manager
Handled the paperwork, vendors, and day-to-day financial work for two senior communities. When something stalled, I tracked down what was missing.
City of Eagle Mountain
Customer Relations Representative
Helped residents with billing and city services, updated web content, and supported public events. It taught me how quickly a small system problem becomes somebody’s whole afternoon.