-
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
RC Test: Number Play 1.0.0-rc.1 #797
Labels
Comments
This was referenced Apr 15, 2022
This was referenced Apr 15, 2022
Calling QA here. Fewer platforms were hit, but I think we hit everything important. QA credits include Nancy, Emily, and myself. |
Awesome, thanks so much for the quick turnaround @Nancy-Salpepi @stemilymill @KatieWoe ! |
8 tasks
This RC was deployed to production, thanks all! Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RC Test
Mentions: @amanda-phet, @kathy-phet
Simulation links
Test Matricies
Features included
Focus and Special Instructions
The purpose of this test is for publishing a prototype of Number Play in phet brand. The goal is to have the prototype published by 12 pm on Monday, 4/18.
Please try out the query parameters specified in https://github.com/phetsims/number-play/blob/1.0/js/common/NumberPlayQueryParameters.ts when testing. The only locales currently supported with
secondLocale
areen
andes
, and that query parameter only works on theall
version of the sim. When included, a toggle should appear to change the language of the speech synthesis button and language of the Word accordion box.Please also note that the memory leak in phetsims/number-play#127 has not been fixed yet, and is actively being worked on, so there's no need to do a new memory test right now.
There have been some recent changes to how the sum is counted with the papers/object, so please make the number of objects in the play area in relation to the sum readout in the "Total" accordion box a focus of this test.
Thanks!
For QA...
General features
What to Test
spreadsheet and notify AR or AM if it not there.
PhET-iO features
What to Test
sure the simulation loads without crashing or throwing errors.
random platform.
?phetioDebug
on the Studio and State wrapper.index.html
by double clicking it on your desktop or in a Finder-view.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.
If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.
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, 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
Critical Screen Reader Information
We are tracking known screen reader bugs in
this Google Document. 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:
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: