Quality Engineering

Quality Engineering for Internet Resource Management

Requirements reviews, risk-based test planning, and UI/API test design across Internet resource-management workflows.

Role

Independent Quality Assurance Consultant

Stack

UI/E2E testing API testing requirements reviews risk-based test design

Engagement

My quality engineering work on AFRINIC’s MyAFRINIC v2 centres on behaviour observable through the UI, end-to-end user journeys, and APIs. The engagement began in May 2026.

Platform context

The platform has more than 250,000 registered app users and supports Internet resource-management workflows for member organisations across Africa and the Indian Ocean region.

My contribution

I prepared a cross-module test strategy and module test planning to define scope, product risks, dependencies, and traceability. Requirements and non-functional specification reviews identify ambiguity, missing acceptance criteria, and testability gaps before those gaps become unreliable pass/fail decisions.

Across platform workflows, I designed UI/E2E and API test cases and regression sets covering expected behaviour, end-to-end user journeys, negative scenarios, and accessibility considerations. Test-case registers, test-data inventories, and dependency records keep that coverage connected to its source requirements and known constraints.

I also documented defects with reproducible evidence to support investigation and follow-up.

Quality approach

The work connects requirements, risks, test conditions, and expected results. It makes gaps visible so that testing and quality decisions can be based on evidence.

Requirements reviews, test planning, regression design, and reproducible defect reports give the team a clearer view of platform behaviour and the areas that need further investigation.