Ebenezer Osei-Bonsu
Back to all work

Case study · Business software · Devnest

HAP ERP

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
HAP ERP mobile attendance screen with a clock-in button and an attendance log.

Product screens · seeded test data

01 — What it was

A comprehensive ERP that brings accounting, human resources and payroll into one system.

02 — Why it mattered

Accounting, HR and payroll share the same staff and financial records, so an error in one carries into the others.

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 the links between modules, for example a change to an employee’s record flowing correctly into payroll and then into accounting, as well as each module on its own.

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.

HAP ERP mobile home dashboard with shortcuts to attendance, leave, payslips, duty roster and change requests.
Product screens · seeded test data

06 — Tools

Playwright, Postman, Microsoft SQL Server

07 — Result

Launched and used in production, bringing accounting, HR and payroll into one system.

HAP ERP mobile home screen with sales, inventory and procurement summaries.
Product screens · seeded test data

08 — What I learned

In an ERP, I learned to follow a single record across modules; most of the risk sits where one module hands data to the next.