Dev Test: Unit Rates 1.1.0-dev.11
Closed this issue · 10 comments
Dev Test
Mentions: @arouinfar @kathy-phet @KatieWoe @Nancy-Salpepi
Simulation links
Test Matrix
Please include all (non-screen reader) feature testing in these records if applicable.
- Latest macOS, Safari (Tester = MM, Time = 1.5 )
- Latest iOS, Safari (Tester = AM , Time = 1)
- Windows 10/11, Firefox (Tester = MM , Time = 2)
- Windows 11, Chrome (Tester = KW, Time = 2)
- Latest Chrome OS, Chrome (Tester = KW, Time = 1)
Light testing, or optionally skip if time crunch:
- Latest macOS, Chrome (Time = )
- Windows 10, Chrome (Time = )
Features included
PhET-iO- Dynamic Locale
Alternative InputUI SoundSonificationDescriptionVoicing
Focus and Special Instructions
Contact me when you're ready to begin this test. I'll publish the dev version and fill in {{VERSION}} in this issue.
We are re-publishing this sim off of main with PhET brand only. The goal for the publication is to make the sim easier to maintain. In addition to a typical dev test, please compare to the published version for regressions or unexpected changes.
New features include pan-&-zoom and dynamic locale, since they now are enabled by default in main.
Issues to Verify
These issues 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
- 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.
- Make sure each wrapper 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:- Alternative Input
- Interactive Description
- 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)
Critical Screen Reader Information
We are tracking known screen reader bugs in
here. 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:
<b>Test Device</b>
blah
<b>Operating System</b>
blah
<b>Browser</b>
blah
<b>Problem Description</b>
blah
<b>Steps to Reproduce</b>
blah
<b>Visuals</b>
blah
<details>
<summary><b>Troubleshooting Information</b></summary>
blah
</details>
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:
- Consult the QA Book.
- Google it.
- Ask Katie.
- Ask a developer.
- Google it again.
- Cry.
@KatieWoe said that QA is ready to begin this test, so I published 1.1.0-dev.10 and fixed up the links in this issue.
@kathy-phet paused this dev test for another higher-priority test.
According to @Nancy-Salpepi in Slack#quality-assurance, the status of 1.1.0-dev.10 was:
A few of us have started on it but no platforms have been checked off.
A new dev version will need to be published before resuming this test, and the {{VERSION}} placeholders in this issue will need to be filled in again.
@KatieWoe said that QA is ready to begin this test, so I published 1.1.0-dev.11 and fixed up the links in this issue.
Memory tests look like there might be a minor leak. Let me know if it warrants an issue @pixelzoom.
My memory test. Similar to Katie's
The memory tests above both go down at some point, indicating stabilization. And the heap sizes are consistent with my tests in phetsims/unit-rates#226. So I don't think this indicates a memory leak, and I'm not concerned. But if you'd like me to spend more time on memory, please indicated in phetsims/unit-rates#226.
@KatieWoe and @Ashton-Morris: It would also be helpful to know the platform for your memory tests. My guess: @Ashton-Morris tested on macOS, so has similar heap size( 94MB) to my tests on macOS. @KatieWoe tested on Windows, and therefore has a slightly higer heap size (96MB).
Win 11 Chrome for me. One at the start and one every minute after for 10 minutes.
Correct MacOs on Safari. I did one at each minute for 10 but did not do one right at the start. I can do that next time I do a memory test though.
QA is done
Thanks QA team! All issues have been addressed and closed, so we're ready for RC testing.