Skip to content

Testing Element on Web

Jump to bottom
Kat Gerasimova edited this page Jan 15, 2022 · 2 revisions

Once you have set yourself up for community testing, you are ready to get started on Web.

Open the RC for the next Element release in private browsing mode: https://staging.element.io

Test and record results

You’re now ready to test the staging version of Element! To do so, you need to follow the test cases in the lower left frame of the spreadsheet. In our example, the first step is to create an account on Matrix.org. Click on the test case name, and it will bring you to a document with all the steps you need to follow.

Screenshot showing list of test cases and people who are testing with a link preview of one test case

Please mark test cases as "done" in your column in the spreadsheet by filling them with a green colour for pass or red for fail. You can also use orange if there is something which needs attention.

If you find any issues, head to the Issues found tab of the spreadsheet:

Screenshot of a section of the spreadsheet showing tabs for the different sheets in the document

You should see a sheet which looks like this:

Spreadsheet showing list of issues found during testing with details and additional information

When walking through the steps of the test case, you may notice oddities, unsettling behaviour of the application, unexpected screens, confusing messages, or even failures. If one of these occurs, please check if the defect has already been recorded in the spreadsheet, and if not, take a screenshot or a screen recording of the issue. When you're ready to make a note of the problem, fill in a new line in the sheet:

  • Defect is when a feature or interaction is broken, while an Enhancement is when a feature or interaction could be improved.
  • Who found it: if you test alone, list yourself so we can follow up with you for more information; if you test with other people, you can list them as well if that is useful.
  • Which test cases you were following: copy and paste the name of the test case you were following. It must be one of the tests listed on the Overview tab unless you have gone off script.
  • Description: a short description of what happened.
  • Issue already exists: have a quick search through existing issues to see if it’s been filed before.
  • How does it affect you: write a sentence or two to explain why this issue is a problem for you.
  • Steps to reproduce: list detailed steps to explain how someone else can reproduce the issue. Make sure to mention where you are starting, which part of the screen you click (e.g. “the + button in the bottom right corner”), what to expect in between interactions. Use Alt+Return to go to a new line in the cell.
  • Do you have a screenshot or a screen recording: screenshots and recordings are worth a thousand words. If you have any relevant ones, we can reach out to you to get copies of them.
  • Link to the issue on GitHub: if you are filing your own issues or if the issue already exists, you can add a link here so that the issue isn’t duplicated.
Clone this wiki locally