Skip to main content

​
Subject of Testing (Scope)

This test plan covers:\
  • New user top-up flow on www.telgea.com/top-up\
  • Admin-side top-up management (notifications & UI)\
  • SMS/Email triggers for top-ups\
  • Consumption model & display of usage\
  • Roaming notifications\
  • Credit limit system & related SMS triggers

​
Test Plan Overview

Objective: Ensure full functionality, correctness of logic, UX/UI, notifications, backend triggers, and data consistency for all user/admin interactions. Approach:\
  • Manual functional testing of UI flows\
  • API testing via Swagger/Postman\
  • Notification checks (SMS/Email)\
  • Data state validation (DB or mocked)\
  • Edge case and error-state testing

​
What Is Tested

  • Form submissions (user flow)\
  • Phone number verification with SMS\
  • Selection of top-up types and activation dates\
  • Correct request sent to admin panel\
  • Admin decision flow (approve/reject)\
  • Email/SMS notifications based on each state\
  • Consumption display accuracy (data/minutes used)\
  • Roaming behavior notifications\
  • Credit limit enforcement and alerts

​
Risks

  • Missed or duplicate notifications\
  • Incorrect user verification logic\
  • Misaligned timezones or date activations\
  • Unclear feedback to users\
  • Consumption not synced correctly\
  • Inconsistent admin portal UX\
  • Delayed backend triggers (e.g. SMS queue)

​
What’s Needed for Testing

  • Test and staging environments with real/test numbers\
  • Access to Swagger/Postman with auth token\
  • Mock data or simulator for CDRs (consumption)\
  • Access to notification logs (SMS/Email)\
  • Admin credentials for UserView portal\
  • Figma flows for reference

​
Checklist: Functional Tests

​
User Top-Up Flow

  • User can access www.telgea.com/top-up on mobile\
  • Phone number verification via SMS works\
  • Company-user check works correctly\
  • User sees all top-up options\
  • User can choose activation date\
  • Request is submitted and confirmation is shown

​
Admin Flow

  • Admin receives action action-userTopupRequest\
  • Clicking action opens correct user profile\
  • Admin can Accept or Decline\
  • Accept adds top-up to user’s plan\
  • Decline triggers rejection notification

​
Email/SMS Notifications

  • email-userTopUpRequestSent triggered after user request\
  • email-userTopUpRequestAccepted sent on approval\
  • email-userTopUpRequestDeclined sent on rejection\
  • sms/email-userDataAdded triggered when data added\
  • sms/email-userMinutesAdded triggered when minutes added

​
Consumption Model

  • Usage data displayed correctly in UserView (circle graphs)\
  • Local data, minutes, international data values are accurate\
  • Data refreshes after usage or top-up\
  • Percentage display matches backend data

​
Roaming Notifications

  • sms/email-userAbroad-home-zone triggered when entering HomeZone country\
  • sms/email-userAbroad-other-countries-empty triggered if no roaming data\
  • sms/email-userAbroad-other-countries-active when data exists

​
Credit Limit Checks

  • Limits are configurable on backend\
  • sms-userDataLow triggered at 80% data usage\
  • sms-userMinutesLow at 80% minutes usage\
  • sms-userDataEmpty when data = 0\
  • sms-userMinutesEmpty when minutes = 0\
  • Roaming and international calls blocked if credit limit reached

​
Test Descriptions (Short format)

​
Test: User submits Top-Up Request

Objective: Ensure user can complete a top-up request
Steps:\
  1. Go to /top-up\
  2. Enter phone number and confirm via SMS\
  3. Choose a top-up option + activation date\
  4. Submit
    Expected: Request confirmed, email sent, admin receives action
    Edge: Number not linked to company → error shown

​
Test: Admin Accepts Request

Objective: Admin can approve user top-up
Steps:\
  1. Open portal, go to Actions\
  2. Open action-userTopupRequest\
  3. Click Accept
    Expected: Top-up applied, user notified via email/SMS
    Edge: Duplicate approval should be blocked

​
Test: Credit Limit Exceeded

Objective: Check triggers when credit runs out
Steps:\
  1. Simulate consumption to hit 80% and 100% thresholds
    Expected: SMS for 80% & 100%, roaming disabled
    Limitation: Can’t verify real network block, mock-only