This one is a commercial product running at mojgo.rs, so the repository is private. The numbers below are from the codebase itself, and I am happy to walk through the architecture or the test suite on a call.
Why this one is the real test
A leave tracker sounds simple until you write down the rules. Entitlement accrues over a year. Unused days carry over, but only some of them, and only until a cutoff. Public holidays are national but companies add their own. A request spans a weekend differently than a Tuesday. Approvals route to a manager who may themselves be on leave.
Getting that wrong means someone loses days they earned. This is the kind of domain where the tests are not ceremony.
How it is tested
43 end-to-end Playwright specs and 28 unit test files. The end-to-end weight is deliberate: the risky behavior in this app is multi-step and role-dependent - an employee submits, an admin approves, a balance changes - and that only holds together in a real browser against a real database.
The e2e suite includes visual snapshot tests across desktop and mobile, so a layout regression fails CI rather than reaching a user.
Engineering practice on display
- 81 SQL migrations. Every schema change is a reviewable, replayable file.
Types are regenerated from the live schema (
pnpm db:types), so the database is the source of truth for TypeScript, not a hand-maintained parallel model. - 150 markdown documents - architecture decision records, runbooks, email template references. The decisions are written down where the next person looks.
- Seeded demo data - realistic tenants, employees, and requests, all tagged
is_demo, so the app can be demonstrated and tested without touching real records. - Bilingual (Serbian / English) from the start, because retrofitting i18n is how you learn not to retrofit i18n.
- Sentry on client and server, plus accessibility and screenshot CI workflows.