Case study · Forestry governance · Devnest
FLEGT Portal
Ownership: Team · Senior QA
My role: Senior QA Engineer at Devnest Systems, as part of the delivery team.
- Sector
- Forestry & natural resources
- Context
- Devnest Systems
- Ownership
- Team · Senior QA
Real screenshot · seeded test data
01 — What it was
A portal that lets EU FLEGT competent authorities request and receive information on the validity and authenticity of FLEGT licences, directly from Ghana’s FLEGT licensing authority and in a controlled way. It’s one of the three portals around the Ghana Wood Tracking System.
02 — Why it mattered
EU authorities rely on it to confirm that a Ghanaian FLEGT licence is valid and authentic, so the answer it returns has to be correct.
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
QA had to cover controlled access: authorities outside Ghana see licence information only through the channel the portal provides. The validity and authenticity it reports also had to agree with what Ghana’s licensing authority holds.
05 — What I did
As part of the Devnest team, I contributed to the portal’s end-to-end quality validation and launch, alongside GWTS and its other two portals. I ran Playwright regression suites and supported data migration with Postman and SQL Server. I also took part in production deployments, and trained and supported end users through documentation and remote troubleshooting.
06 — Tools
Playwright, Postman, Microsoft SQL Server
07 — Result
Launched as part of the GWTS ecosystem, connecting EU FLEGT competent authorities with Ghana’s FLEGT licensing authority.
08 — What I learned
When the users are authorities in another country, access rules are part of what you test, not a setting you assume.