-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev Test: my-solar-system 1.1.0-dev.9 #927
Labels
QA:dev-test
Dev test before an RC
Comments
This was referenced Apr 6, 2023
Closed
This was referenced Apr 7, 2023
This was referenced Apr 10, 2023
This was referenced Apr 12, 2023
Chrome book performance looked ok. There were a few instances of brief lag, but not much, and nothing I would worry about. |
Calling QA here |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dev Test
Mentions: @KatieWoe and @kathy-phet
Simulation links
Test Matrix
Please include all (non-screen reader) feature testing in these records if applicable.
Light testing, or optionally skip if time crunch:
Features included
Focus and Special Instructions
Issues to Verify
These issues should have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.
For QA...
General features
What to Test
Accessibility features
What to Test
Specific instructions can be found above.
Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:
Test all possible forms of input.
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:
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:
The text was updated successfully, but these errors were encountered: