Case study · Food & nutrition · Devnest
Food Ingredient Database
Ownership: Team · Senior QA
My role: Senior QA Engineer at Devnest Systems, as part of the delivery team.
- Sector
- Healthcare & life sciences
- Context
- Devnest Systems
- Ownership
- Team · Senior QA
Real screenshot · seeded test data
01 — What it was
A web application for collecting, recording and categorising food products, their ingredients and their nutritional information.
02 — Why it mattered
Ingredient and nutrition records are only useful if they’re captured and categorised consistently.
03 — My role
Senior QA Engineer | Systems Implementation Engineer at Devnest Systems, as part of the delivery team. I didn’t build the system.
04 — Technical problems
QA had to cover data entry and categorisation: products, ingredients and nutritional values had to be recorded correctly and land in the right categories.
05 — What I did
As part of the Devnest team, I ran Playwright regression suites, supported data migration with Postman and Microsoft 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
07 — Result
Launched and used in production to collect, record and categorise food products with their ingredients and nutritional information.
08 — What I learned
On a data-collection app, I learned that the test data matters as much as the test steps: realistic, messy entries find the categorisation gaps that tidy ones miss.