-
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.3.0-dev.7 #1008
Comments
@KatieWoe Since this is a dev test, we want to minimize the time between publishing the dev version and creating the 1.3 release branch. So 1.3.0-dev.7 has not been published yet. Let us know when you're ready to start, and @AgustinVallejo or I can publish. |
For PhET-iO testing, please refer to the examples.md on main, rather than the version linked from the wrapper index page. Thanks! |
Calling QA here |
Thanks QA for finding some great issues. We've addressed everything that was blocking, and are ready to proceed with RC testing. Closing. |
Dev Test
Mentions: @AgustinVallejo @pixelzoom @arouinfar
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:
If PhET-iO is being tested:
Features included
DescriptionVoicingFor QA...
General features
What to Test
PhET-iO features
What to Test
sure the simulation loads without crashing or throwing errors.
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: