Case study · Public finance · Devnest
Sika Fund
welfare & credit union control
Ownership: Team · Senior QA
My role: Senior QA Engineer at Devnest Systems, as part of the delivery team.
- Sector
- Finance & public finance
- Context
- Devnest Systems
- Ownership
- Team · Senior QA
Real screenshot · seeded test data
01 — What it was
A fund management, welfare and credit union control system for public-sector staff and welfare unions: membership, contributions, loans, benefits and payouts in one place. It has a member portal and an admin portal that work together.
02 — Why it mattered
It handles members’ savings and loans for CAGD, the Audit Service Final Account Union and EOCO’s welfare unit, so balances and loan records have to be right.
03 — My role
Senior QA Engineer | Systems Implementation Engineer at Devnest Systems, as one member of the delivery team. I didn’t build the system.
04 — Technical problems
Retrieving SMS one-time passwords during automated tests. And a cross-portal journey: the member and admin portals talk to each other, so one flow starts with a member, moves to an administrator, then returns to the member.
05 — What I did
As part of the Devnest team, I contributed to end-to-end quality validation and launch. I tested the member-to-admin-to-member journeys across both portals, handled SMS OTP retrieval in automated tests, and ran Playwright regression suites. I supported data migration and multi-tenant setup with Postman and SQL Server, took part in production deployments, and trained and supported end users through documentation and remote troubleshooting.
06 — Tools
Playwright, Postman, Microsoft SQL Server
- Playwright
- Postman
- SQL Server
07 — Result
Launched and in use by CAGD, the Audit Service Final Account Union and EOCO’s welfare unit.
08 — What I learned
When one task passes between two portals and two kinds of user, I design the test around the whole journey, not one application. Steps a test can’t simply click through, like an SMS one-time password, need planning from the start.