You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please include all (non-screen reader) feature testing in these records if applicable.
Latest macOS, Safari (Time = 2hrs)
Windows 10, Chrome (Time = 1hr)
Windows 10/11, Firefox (Time = 1.5)
Latest iOS, Safari (Time = .75)
Windows 11, Chrome (Time = 1)
Light testing, or optionally skip if time crunch:
Latest macOS, Chrome (Time = )
Latest Chrome OS, Chrome (Time = .75)
Features included
[ ] PhET-iO
[ ] Alternative Input
UI Sound
Sonification
[ ] Description
[ ] Voicing
Focus and Special Instructions
This is meant to be a test of the "quick and dirty" release of the partner-ported Sound Waves sim. We intend to publish this to the PhET website as a port of the legacy Java 'Sound' sim. It is not PhET-iO instrumented and will have limited alternative input features.
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.
N/A
For QA...
General features
What to Test
Click every single button.
If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Try to include browser version numbers
If there is a console available, check for errors and include them in the Problem Description.
Run through the string tests on at least one platform, especially if it is about to go to rc.
Check the Game Up harness on one platform.
PhET-iO features
What to Test
Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
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:
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing
Test all possible forms of input.
Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).
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
Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)
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.
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Dev Test
Mentions: @matthew-blackman @samreid @marlitas
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
[ ] PhET-iO[ ] Alternative Input[ ] Description[ ] VoicingFocus and Special Instructions
This is meant to be a test of the "quick and dirty" release of the partner-ported Sound Waves sim. We intend to publish this to the PhET website as a port of the legacy Java 'Sound' sim. It is not PhET-iO instrumented and will have limited alternative input features.
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
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.
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
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: