💻E2E Wallet Automation Test Plan

Goal:

1. To aide manual QA on testing repetitive, easy and important test for Wallet application.

2. To generate analytic test report and be an asset into product requirements review.

3. To give the team more time to spend on challenging and rewarding task.

4. To improve accuracy

5. To increase Test coverage

Scope:

Answers which part of the system requires E2E automation

Environments to test:

Staging:

• BO : Local environment

• Site: Local environment

Production:

• BO:https://admin.nexiux.io/

• Site:https://qa.nexiux.io/

Testing types we are going to use:

• Regression testing

• Sanity testing

Wallet got 2 main pages:

• Back Office

• Site

Features included in the Regression test:

Staging Back Office:

1. Admin Login

2. Admin Logout

3. BO Dashboard page

   1. Generate reports

   2. Analytic reports

4. Operator page

   • Account Management features

     1. Create Operator

     2. Edit Operator

     3. Delete Operator

     4. Operator accounts search Filters

   • Permission Group features

     1. Create Permission Group

     2. Edit Permission Group

     3. Delete Permission Group

     4. Download Persmission group report

     5. Permission group search Filters

5. Members page

   1. Member Management features

   2. Member Marker Management features

   3. Label Management features

   4. Members Online feature

   5. Profile Setting feature

   6. Member Reports feature

   7. Member Management Config feature

6. Affiliates page

   1. Affiliates Programme feature

   2. Affiliates Criteria feature

   3. Affiliates Request feature

7. Deposits page

   1. Deposit Requests(Internal)

   2. Deposit Requests(3rd Party)

   3. 3rd Party Deposit Providers

8. Withdrawals page

   1. 3rd Party Withdrawal Provider

   2. Withdrawal Request

9. Promo page

   1. Promo Label feature

   2. Promo Requests feature

   3. Promo Listing feature

10. VIP page

11. Rebates page

12. Reports page

    1. Balance Service Record

    2. Balance Transaction Record

    3. Daily Operating Reports

    4. Reports

    5. Member Records

    6. Promo Payout Records

    7. Rebate reports

Features included in the Sanity test:

Back Office Sanity:

1. Admin Login

2. Admin Logout

3. BO Dashboard page

   1. Generate reports

   2. Analytic reports

4. Operator page

   • Account Management features

     1. Create Operator

     2. Edit Operator

     3. Delete Operator

     4. Operator accounts search Filters

   • Permission Group features

     1. Create Permission Group

     2. Edit Permission Group

     3. Delete Permission Group

     4. Download Persmission group report

     5. Permission group search Filters

5. Members page

   1. Member Management features

   2. Member Marker Management features

   3. Label Management features

   4. Members Online feature

   5. Profile Setting feature

   6. Member Reports feature

   7. Member Management Config feature

6. Affiliates page

   1. Affiliates Programme feature

   2. Affiliates Criteria feature

   3. Affiliates Request feature

7. Deposits page

   1. Deposit Requests(Internal)

   2. Deposit Requests(3rd Party)

   3. 3rd Party Deposit Providers

8. Withdrawals page

   1. 3rd Party Withdrawal Provider

   2. Withdrawal Request

9. Promo page

   1. Promo Label feature

   2. Promo Requests feature

   3. Promo Listing feature

10. VIP page

11. Rebates page

12. Reports page

    1. Balance Service Record

    2. Balance Transaction Record

    3. Daily Operating Reports

    4. Reports

    5. Member Records

    6. Promo Payout Records

    7. Rebate reports

Web Sanity:

1. Main Page

   1. Register

   2. Login

2. Sportsbook page

3. Casino page

4. Virtual Sports page

5. Feature

6. Safer Gaming

7. Account related functions:

   1. Account Verification

   2. Balance

   3. Betting History

   4. Bonus Info

   5. Deposit

   6. Deposit Profile

   7. Game History

   8. Inbox

   9. Limitations

   10. Member Balance

   11. Personal Details

   12. Profile Options

   13. Reality Checked

   14. RTP

   15. Transaction History

   16. Withdrawal

8. Help Center

9. Safer Options

10. Support and Tips

Entry Criteria

What are the things needed before starting E2E automation testing.

1. Test automation tools

   1. E2E test suite Cypress version installed

   2. Test Git repository

   3. Testing reports and Analytics

2. Stable project environment build where the tests runs

   1. Local environment for Staging build

   2. Production test environment for QA

3. Test case documents

   1. PASSED test cases

   2. Testing type tags for each test cases (Regression or Sanity)

   3. Identified test cases that can be automated

4. Manpower

   1. Test Automation Engineers

Exit Criteria

What are the things to expect after writing of End to End test.

1. All test cases for Regression test defined in the scope are with automation script.

2. All test cases for Prod Sanity test defined in the scone are with automation script.

3. Regression scheduled test run for Staging Back Office and Site

4. CI setup for E2E test is done

5. Slack command trigger to run Sanity test automation

6. Github CI command trigger to run Regression test automation

7. Slack notifcation for the Test reports and status results.

Wallet test are then for maintain and for updates if there are new features in the product.