Case study · Fintech · Fido
Adowa
Ownership: Team · Senior QA
My role: Senior QA Engineer at Fido Micro Credit, as part of the engineering team. I helped test the entire app, from client submissions through admin review and routing to feedback. I covered it with Playwright suites in CI/CD and tracked issues in Jira.
- Sector
- Finance & public finance
- Context
- Fido Micro Credit
- Ownership
- Team · Senior QA
Real screenshot · seeded test data
01 — What it was
A new document review system at Fido. Clients submit documents; admins view and work on them, route them through dedicated channels and send feedback to the client.
02 — Why it mattered
Client documents need a dependable path from submission, through review, to feedback.
03 — My role
Senior Quality Assurance Engineer at Fido Micro Credit, working inside the engineering team. I didn’t build the system.
04 — Technical problems
One document passes through several hands: the client submits it, it has to appear in the admin portal, admins work on it and route it, and feedback has to reach the client. QA had to cover that whole chain, not each screen on its own.
05 — What I did
As part of the team, I helped test the entire app: client submissions appearing in the portal, admins viewing, working on and routing documents, and feedback going back to the client. I covered it with Playwright suites that run in the CI/CD pipeline, and tracked issues in Jira.
06 — Tools
Playwright, CI/CD, Jira
07 — Result
In use at Fido as one system for client documents, from submission through admin review and routing to feedback.
08 — What I learned
A document that changes hands between client and admin is easiest to break at the handoff, so I test the handoffs first.