Test-a-thon Instructions

Step 1: Visit the "<RELEASE NAME> TESTS" tab in the testing sheet (<link to testing sheet>) and pick a test in an area you are familiar with, one you want to learn more about, or an area that is of interest to you. Assign yourself by writing your name in the "Assigned To" column. Please only "claim" tests you can complete in the next 24 hours. 

Note: The user role in column A of the testing sheet is a good indicator as to the type of user that may be relying on the tested workflow. For example: A test with the user role marked as Learner would test a functionality that the learner relies on.

Step 2: When you begin to test, update the Status column to 'In Progress'.

Step 3: Perform the test!

Use our testing sandbox for this:

• <Insert link to testing sandbox>

For details about test accounts and more, see: Testing Cheatsheet

Step 4: Update the Status column to 'Complete'.

Step 5: Update the Result column to 'Passed' or 'Failed'.

Step 6: If the test fails, please create an issue on GitHub in the build-test-release repo, with the "Test Case ID" in the title of the ticket and a description including steps to reproduce, expected result, actual result, and screenshots and/or screen recordings. Add the label "release testing". Here is an example of a well-written ticket.

Note on Github: If you don’t yet have a GitHub account, you can create one here: GitHub · Change is constant. GitHub keeps you ahead. by clicking Sign up. Follow the prompts to create your personal account.

Step 6B: Please ensure you have email alerts “on” from GitHub. When you receive notification that your failed test has been fixed, please come back here and re-test. If you are not available to re-test, please post on the GitHub ticket or in Slack.