Abdallah Elraai

Case file Exhibit A·4

CV ↓

Exhibit A·4Syntheia (opens Syntheia in a new tab)

The release gate

I wrote the QA process and I hold the gate, so design intent and the shipped build stay the same object.

Matter
Syntheia (opens Syntheia in a new tab) — Legal-tech SaaS · enterprise → self-serve B2B/B2C
Role
QA process design · release sign-off · test automation
Domain
Release quality
Term
2025 — present
  • QA
  • Release management
  • Test automation
  • Accessibility
  • AI-leveraged

Most design work is signed off at handoff, which checks a file. I sign off at release, which checks the product. The gap between those two is where quality quietly leaves, and nobody is assigned to it.

I defined the QA process, coordinate testing across the team, and have verified 116 tickets to date — features, UI accuracy, and bug-fix verification. Owning the gate means the last person to look at the build before it ships is the person who drew it.

On top of that I am building AI-assisted test automation: seventeen suites covering accessibility, visual regression, design-system conformance and end-to-end flows, so the regression pass stops being a manual re-read of the same screens every release.

Design signs off at handoff.Design signs off at release.

Handoff sign-off checks a file. Release sign-off checks the product. The difference is everything that drifted in between — and drift is invisible unless somebody is looking for it on purpose.

Process flow Where design actually signs off
Build Gate Release yes no yes no Ticket built dev complete 17 suites a11y · visual · DS Clean? Design review intent vs build Signed? Released design on record Reopened with the artefact

The automated suites handle what is arithmetic — contrast, alignment, token conformance, dead links. What reaches me is judgement, which is the only part worth a person’s attention.

The rig — what the automation actually is 17 suites · 216 artefacts captured
  • Accessibilityaxe-core, per surface
  • Visual regressionpinned snapshots, cross-platform
  • Design-system conformancetoken drift, contrast, alignment
  • Flow reviewend-to-end user journeys
  • Design-to-code reviewbuilt UI vs the spec
  • Per-surface suitesone per major product area

Stack Playwright@axe-core/playwrightculoriTypeScript

  • 116

    Tickets verified to date

On reflection — Automation did not replace the manual pass; it made the manual pass worth doing. The machine handles what is arithmetic — contrast, alignment, token conformance — so my attention goes to judgement.

Syntheia is under NDA. Every interface on this page is a redrawn abstraction — real structure and real decisions, no real screens and no client data.