ANQ Test+Summary+Report+Sprint138

ANQ Test+Summary+Report+Sprint138


Test Summary Report Sprint138

Test Summary Report

All Number Query (ANQ)

Document Control

Version History


Version No.

Issue Date

Author

Reason for Change

1.0

24 June 2026 

Ugomma Amaechi

Process Enhancement


Review


Reviewer Name

Department

Version No.

Review Date

Stanley Ibekwe

Application Development

1.0

 


Approvals



Approver Name

Department

Version No.

Approval Date

Ugomma Amaechi

Technology

1.0



Cc:



Approver Name

Department

Version No.

Oreoluwa Ademiniyi

Product Management

1.0

Abiola Abraham

Quality Assurance

1.0



1       Introduction


1.1         Purpose

ANQ is a telecom data infrastructure and identity/fraud intelligence platform. It operates as a B2B data aggregation and orchestration platform that provides data services to clients such as banks, fintechs, and other businesses to perform services like routing, KYC verification, and fraud prevention on customers.

These services are provided through Service Providers, who get their data from Content Providers (also known as Data Providers).

A Functional test was performed to validate the listed features below.

At the close of sprint 139, all feature on the staging environment have been tested and are production-ready:


  1. Update To Wallet To Handle Insufficient Funds In Client's Mapping
  2. Update BVN, NIN and Number Verification To V2 billing and remove index file
  3. Update library nuget


2       Test Summary


Project Name:  ANQ

Version Number: V1.0

Test Duration: June 24, 2026

Test Conducted: Functional Test

Outcome of Test: Production Ready


2.1     Update to Wallet to Handle Insufficient Funds in Client's Mapping:

An issue was identified to resolve status update when a new client is created. Before now, the client status handles both the active client status and the wallet status, however, these were separated, and a wallet ID was mapped to all client, hereby using the wallet ID was used to get the wallet balance of the mapped client, instead of having "Status" handle both client active status and wallet balance. 

S/N

Items

Values

1

Test Owner

Abiola Abraham

2

Test Date

24th June 24, 2026

3

Total Case Executed

All features on the staging environment

4

Test Case link


5

Total Bugs Detected

NIL

6

Total Bugs Fixed

NIL

7

Bug Link

N/A

8

Total Moved to Backlog

N/A

9

Test Results


10

Additional Comments

Approved – Ready for Production 


2.2         Update BVN, NIN and Number Verification To V2 billing and remove index file:

The billing system was integrated into ANQ to handle all clients' activities instead of having a separate billing system

S/N

Items

Values

1

Test Owner

Abiola Abraham

2

Test Date

24th June 24, 2026

3

Total Case Executed

All features on the staging environment

4

Test Case link


5

Total Bugs Detected

NIL

6

Total Bugs Fixed

NIL

7

Bug Link

N/A

8

Total Moved to Backlog

N/A

9

Test Results


10

Additional Comments

Approved – Ready for Production 


2.3         Update library nuget:

A shared library was created to handle basic validations across all services. This was implemented to avoid duplication of effort.

S/N

Items

Values

1

Test Owner

Abiola Abraham

2

Test Date

24th June 24, 2026

3

Total Case Executed

All features on the staging environment

4

Test Case link


5

Total Bugs Detected

NIL

6

Total Bugs Fixed

NIL

7

Bug Link

N/A

8

Total Moved to Backlog

N/A

9

Test Results


10

Additional Comments

Approved – Ready for Production 



3       TEST ASSESSMENT


In accordance with QA Test plan and strategy, the following test were successfully completed:

  • API Functional Testing
  • Retesting & Regression Testing
  • Database Testing

The following SDLC process were adhere too during the course of testing this project

S/N

SDLC PROCESSES

Evidence

Status (Done)

1

Creation of a pipeline to cater to raising of:

  • a PR from the main branch and merging to dev branch
  • raising a PR from Dev branch and merging into Staging branch by the authorized approvers in QA unit
  • Finally raising a PR from Staging branch that will be merged into production by the QA team.

https://screenrec.com/share/CloYJBZpGF

Done

2

Implementation of code review of developer’s source code


Not Done

3

Solutions Architect confirmed that the architecture of the application is viable.


Not Done

4

Test script (Collection and environment) generation has been uploaded to confluence by the QA unit for seamless integration.


No API test was done

4       SUGGESTED ACTIONS


4.1     API ENDPOINT AND SERVICE TO BE DEPLOYED TO PRODUCTION.

Stated below is the service that QA is raising a Pull request (PR) for the merge to Master by QA:




4.2 COMPONENT CONFIGURATIONS/MIGRATION SCRIPT FOR PRODUCTION:

Infrastructure Checklist:Tick if required to the configured in production


S/N

COMPONENT

CHECK

1

All configMap of any of the services

N/A

2

Modification the database schema

YES

3

Alteration to the secret of Kubernetes

N/A


Database Schema Migration Script for Production: