Skip to content

QA Forum 2025-2-17

Meeting Summary – Exploratory Testing for Student User Type

Overview

To encourage backend developers to take the first step in exploratory testing, Shivi demonstrated the approach for the new Student user type.

1. Feature Background

  • New User Type:
    A new Student user type is being introduced. It is similar to the existing User type but will initially launch with a $0 fee.
  • Email Verification & User Type Change:
    • When an email containing “.edu” is verified, the user type automatically changes to Student.
    • If the email is later changed and verified as a non-“.edu” address, the user type reverts to User.
    • This update can also be made via Hydra.

2. Test Scenarios

The following scenarios were considered for testing:
- New user without KYC completion
- New user with KYC completed
- Existing user without KYC completion
- Existing user with KYC completed

3. Using Regression Testing Methods

  • Creating different users.
  • Logging in using userId.
  • Changing emails and verifying updates.

These methods are part of our regression tests, which can modify and run in user area.

4. Immediate Feedback to PO

  • Initially, it was noted that a Student user would have membership active and could see the referral link from day one.
  • Based on feedback, the PO updated the design:
    • The Student user now receives a free trial similar to a User.
    • The only difference is that the subscription fee is $0.

5. Discussion Points

  • Testing on the App:
    Use the MSISDN and default password “7629” on the staging app for testing after user created or email changed.
  • Post-Study User Behavior:
    It is expected that students will continue using our services after completing their studies.
  • Handling Fraudulent Emails:
    The Zero Bounce email check is used to filter out fraudulent email addresses.
  • Data Warehouse Testing:
    • Currently, there is no dedicated data warehouse test.
    • This topic was raised as an important point, suggesting further discussion with the PO to consider monitoring student user trends for future decisions.