Overview
What this challenge is about.
Read the SEPA Pain.001 XSD (XML Schema Definition) and pick 5 invariants the parser MUST preserve (e.g., 'sum of transactions equals control sum', 'IBAN passes mod-97 check', 'currency consistent across batch'). Build gopter generators for valid + adversarial inputs. Run shrinking-enabled PBT in CI for 5 minutes per run and triage findings. Find at least 3 bugs, file them, and propose fixes. Deliver the PBT module as a merged pull request, the 6-page report with bug-by-bug analysis, and a 1-page guide for the team on when to reach for PBT vs example-based tests.
The Brief
What you'll do, and what you'll demonstrate.
Augment a Go SEPA parser's example-based test suite with property-based tests that surface at least 3 latent bugs hiding behind 84 percent line coverage.
Earning criteria — what you'll demonstrate
- Translate a domain schema (SEPA Pain.001) into testable invariants
- Write effective generators and shrinkers for adversarial inputs
- Distinguish coverage (line-level) from correctness (invariant-level)
- Communicate PBT value to a team that already trusts its unit suite
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.