Skip to main content
  1. Objective
The goal is to verify that the correct transactional emails are sent at the appropriate time (Day 0–Day 13) based on the user’s actions (or inactions). Additionally, verify End User emails after number installation. Day 0 - Welcome e-mail (on the day they sign up) Day 1 - Add a number (if they have not added number yet) Day 2 - Invite a team member (if they have not invited member yet) Day 3 - How to add an extra admin (if they have not invited admin yet) Day 4 - How to transfer your existing business numbers (if they have not transferred a business number yet) Day 5 - How to create a team (if they have not created a team yet) Day 9 - How to transfer an employee’s personal number guide (if they have not transferred a personal number yet) Day 10 - Integrate with HRM (if they have not integrated HRM yet) Day 11 - Integrate with CRM (if they have not integrated CRM yet) Day 12 - Set up payment options to different teams (if they have not set up more than one payment option yet) Day 13 - Analyse consumption in analytics (should be sent to both companies). End user e-mails
  1. What are eSims (Sent the day after they install their number)
  2. What are eSIms and why do you have two (Sent the day after they install their number) Scope of Testing
Included:
  • 14-day transactional emails triggered based on specific user inactivity.
  • End user emails based on number installation.
  • Validations for both email triggering and non-triggering scenarios.
  • Email content verification.
Excluded:
  • Email delivery system functionality.
  • System load/performance testing.
    Test Approach
Manual testing using two controlled accounts:
  • Company A: Does not perform post-activation actions → expect all emails to be sent.
  • Company B: Completes all post-activation actions promptly → No account setup emails are triggered except for the Day 0 email (“Welcome email”) and Day 13 email (“Analyse consumption”), which is sent to all activated accounts.
  • End user - expect 2 emails based on number installation.
Due to the limitation with “date simulation,” we will follow the natural 14-day waiting cycle. Test Environment & Tools
  • Admin Panel (telgea.com)
  • Database access (via Simon, Shubham)
  • Mail logs / Email client
  1. Preconditions
  • Two verified test companies are created and activated:
    • Company A: No post-activation steps completed.
    • Company B: All post-activation steps completed on the first day.
  • Email logs accessible for verification.
  • Account time tracking begins from signup date (Day 0).
    Test Scenarios
Company A — Full email flow expected: Day 0: Welcome email Day 1: Add a number Day 2: Invite a team member Day 3: How to add admin Day 4: Transfer business numbers Day 5: Create a team Day 9: Transfer employee personal number Day 10: Integrate HRM Day 11: Integrate CRM Day 12: Set payment options Day 13: Analyse consumption Company B — Two emails are expected: Day 0: Welcome email Day 13: Analyse consumption End User Emails:
  • 1 day after number install: ‘What are eSIMs’
  • 1 day after install: ‘Why you have two eSIMs’
  1. Test Steps
Company A:
  1. Sign up new account (Company A)
  2. Do not complete any post-activation steps
  3. Monitor email inbox daily
  4. Confirm each email is received according to schedule
  5. Verify email content
  6. Log results
Company B:
  1. Sign up new account (Company B)
  2. Complete all post-activation steps:
    • Add number (End user emails should be triggered)
    • Invite team member
    • Add second admin
    • Transfer business number
    • Create a team
    • Transfer an employee personal number
    • Integrate HRM and CRM
    • Set multiple payment options
  3. Wait 14 days
  4. Confirm no post-activation emails received
  5. Verify End User emails
  6. Log results
    Expected Results
  • Emails sent only if trigger condition is unmet
  • No duplicate emails
  • End user emails triggered after number install
  • Company A: All expected emails received
  • Company B: End-user emails are expected and transactional emails Day 0 and Day 13 are expected.
    Reporting & Defect Tracking
If any email fails:
  • Create bug Include:
    • Company ID
    • Day of failure (e.g., Day 4)
    • Expected vs actual
    • Timestamp
    • Email subject
    • Screenshot/email header (if possible)