/
2025-05-06 & 2025-05-27 Teak Release Test-a-thons

2025-05-06 & 2025-05-27 Teak Release Test-a-thons

All public Working Group meetings follow the Recording Policy for Open edX Meetings

 Date

May 6, 2025

 Participants

  • @Chelsea Rathbun

 Goals

For the Community to have a virtual place and time to complete some tests as part of the Teak Release Testing Process.

 Testing Instructions

Step 1: Visit the "TEAK TESTS" tab in the testing sheet and pick a test in an area you know 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:

For details about test accounts and more, see https://docs.google.com/document/d/1UJUZtjgDGuSKMw6sabrYiLyhP7b-hDJAQpRjPRUb-dE/edit?tab=t.0 (page 2)

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 · Build and ship software on a single, collaborative platform 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.

 Helpful Testing Information

https://docs.google.com/document/d/1UJUZtjgDGuSKMw6sabrYiLyhP7b-hDJAQpRjPRUb-dE/edit?tab=t.0

  For Help or Channeling Feedback

For…reach out to Chelsea Rathbun via slack DM during or after this meeting so we can help and/or work together to improve our testing spreadsheet for this and future releases.

  1. Help during the Test-a-thon

  2. Sharing any feedback on unclear test instructions

    1. Provide a detailed explanation as to how the test could be improved or why it’s currently unclear - does it need more detailed setup instructions? Or does the test case need need to be re-written/expanded?

      1. If you can, please frame your test case in the following format to help us fix this more quickly:

        • Scenario:

        • Given I

        • When I

        • Then I

      2. Example:

        1. Scenario: The login form allows existing logged out user to log in

        2. Given I am a user with an active Open edX account that is logged out

        3. When I navigate to the landing page and click the login button

        4. Then I am directed to a login form

        5. And when I fill in the required fields of the login form with my account information and click the login button

        6. Then I am able to login to Open edX, I am directed to the My Courses page, and I see my account name towards the top of the page

 

 Decisions