phetsims / qa

Quality Assurance Task Tracking
MIT License
12 stars 8 forks source link

Website Regression Test #1020

Open mattpen opened 9 months ago

mattpen commented 9 months ago

Website Regression Test

Mentions: @kathy-perkins @chrisklus @mattpen @KatieWoe

When Problems are Found

New Issues should be opened in https://github.com/phetsims/website-meteor/issues/new Please ping @mattpenn or @chrisklus on slack if you have questions for the developers.

Pages To Test

Note that there is no need to test any simulations, any activity related pages, the help center, the teaching resources pages, or the research page.

Translations

Please test all of the above pages in these translations:

Platforms To Test

Test Matrices

Focus and Special Instructions

There have been significant changes in how the website is built and structured. This test is meant to look for regressions and changes from the current website. There are no new features to evaluate.

Things to focus on:


For QA...

Accessibility features

Screen Readers

This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to screen readers. If you simply need a refresher on screen readers, please consult the [QA Book](https://github.com/phetsims/QA/blob/main/documentation/qa-book.md), which should have all of the information you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

- Windows 10 + Latest Chrome + Latest JAWS - Windows 10 + Latest Firefox + Latest NVDA - macOS + Safari + VoiceOver - iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information

We are tracking known screen reader bugs in [here](https://github.com/phetsims/qa/blob/main/documentation/accessibility-bugs.md). If you find a screen reader bug, please check it against this list.

Keyboard Navigation

This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a screen reader.

Magnification

This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen reader so there is no need to test this case.
FAQs for QA Members
There are multiple tests in this issue... Which test should I do first? Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue? Here's a template for making issues: Test Device blah Operating System blah Browser blah Problem Description blah Steps to Reproduce blah Visuals blah
Troubleshooting Information blah

Who should I assign? We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do? You should: 1. Consult the [QA Book](https://github.com/phetsims/QA/blob/main/documentation/qa-book.md). 2. Google it. 3. Ask Katie. 4. Ask a developer. 5. Google it again. 6. Cry.


KatieWoe commented 8 months ago

I noticed on the Android tablet that switching from the filter page to the browse page was very slow and there wasn't any indication that loading was happening. Not exactly a bug, but rather odd.

mattpen commented 8 months ago

@KatieWoe - We can add a spinner to that transition. Can you open an issue as a bug please?

KatieWoe commented 7 months ago

It behaves the same on the published site, so I don't think it's a bug, but navigating the Browse page with NVDA was rather bewildering. It was a bit hard to focus on individual sims in the list and nothing was read when you scrolled the list with the buttons on the side. Tabbing took you to the first thing in a list, but then the next tab took you to the next list. Reading through each entry took more time.

KatieWoe commented 7 months ago

QA is done