Please ensure testing feedback if provided as soon as possible. The testing window will close on 4/30/2021

Getting a unique email account

Most testing should be done on accounts with unique email addresses. This allows you to easily identify that received emails are being sent to the correct individual and allow you isolate testing to specific accounts as we use email addresses as login Ids.

To help facilitate testing, you can use the GMAIL alias feature along with a GMAIL account that has been setup by the IT department. The alias feature allows us to have a virtual infinite number of email addresses.

Using the GMAIL alias feature

The alias feature works by adding a “+” (plus sign) and unique value to the user portion of the email address. For example aswbtest+robertadach@gmail.com and aswbtest+rg20190307@gmail.com will both work as valid emails.

Accessing emails

To read emails sent to the alias address, you will login with “base” email address credentials, which are:

Email: ASWBTest@gmail.com
Password: ASWBR0ck$

In the inbox you will see all the emails received for any of the alias email addresses.

Important Notes

This account is shared by several teams for testing purposes, please

• Do not change the password on the account

• Do not delete or archive emails that were not sent to an alias you are using

• We recommend that you archive emails vs. deleting them so that they are available for reference later one.

• IT recommends that you format your alias email consistently during your testing so it is easier for you to keep track.

  • A pattern we recommend is aswbtest+<testersinitials><what you are testing><unique number>@gmail.com. For example, if Robert Adach was testing the TX LSW application process he may create an account using the email aswbtest+raTXLSW@gmail.com

  • You may use any pattern, but the idea is to ensure that it is a unique address to avoiding interfering/overlapping someone else’s test.

• Keep track of the email address you are using for each test to make sure you are using the correct account. Often “issues” that are reported are due to users using the incorrect accounts.

What to test

• These are the minimum items to test, you may do additional testing if you would like. Please note that “issues” that are replicated in production will not be addressed at this time.

• The files at the bottom of this document “Member Services Test accounts.xlsx” and “CSC Test accounts for Kraken Launch.xlsx” include a number of different existing accounts you may log in an use

• Testing of website actions can be done by visiting one of the following urls:

  • https://test.application.aswb.org

  • https://test.application.aswb.org/publications

  • https://test.application.aswb.org/scoretransfers

  • https://test.application.aswb.org/practiceexams

Member Services

• As an applicant:

  • Creating a new account

  • Starting and submitting a new license application

    • Paying via CC

    • Paying via Money Order

  • Completing an existing application (See the “Member Services Test accounts.xlsx” file below for existing accounts to log in with

• As a staff member - Desktop access will be available starting 4/25/2021. If you do not have the Test version of the desktop application installed please contact Dan for assistance installing it

  • Importing new Applications

    • Paid via Credit Card

    • Paid via Money

  • Approve Applications

  • Run Reports

  • Send Problem emails

Candidate Services

• Products

  • Purchasing Exam Guides

  • Purchasing Score Transfers

    • The test accounts provided have a number of result scenarios to allow you to verify the different restrictions on purchasing score transfers

  • Purchasing Individual Practice tests

    • The test accounts provided have a number of result scenarios to allow you to verify the different restrictions on purchasing practice tests

• Accessing Individual Practice Tests

  • using the account created in your products test, login and access a practice test

• Group Review practice test

Reporting Issues

When reporting an issue please ensure that you have the following included in your report:

• As detailed of a description of the issue as possible

• What you expected to happen

• Screenshots of the error message or screen (include the full screen including the browser address bar)

• The steps to take to recreate/test the issue (if applicable)

• The user account you were using during the test when you observed the issue

Files

CSC Test Accounts for Kraken Launch.xlsx

MSERV Accounts for Kraken Testing.xlsx

Known issues

The following is a list of CONFIRMED issues identified during testing and the current status of each item.