-
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: Friction 1.6.0-rc.1 #886
Comments
There's no migration supported in this version, but the instructions are still in the guide. Is this a bug? |
By "the guide" do you mean the PhET-iO Guide link? https://phet-dev.colorado.edu/html/friction/1.6.0-rc.1/phet-io/doc/guides/phet-io-guide.html This is expected, as that guide is general for all simulations. It doesn't pick and choose based on the features of that specific simulation. Thanks for asking. |
@zepumph Noting that phetsims/joist#898 is present in this RC but is fixed in master. |
Thanks. That is very helpful. I made phetsims/friction#327 to make sure the cherry picks will happen into friction. |
The extra sound is not stateful. I believe this is intended, but it does seem odd so I wanted to bring it up just in case. |
Do you mean whether the "extra sound" checkbox is checked? Specific user preferences are not intended to be saved and loaded. There are a few exceptions, but extra sound is not one of them. |
Yes, that is what I meant. Most other preferences I've seen in PhET-iO so far have been stateful, so I found it odd. |
Under the Preferences Customization section of the PhET-iO Guide we state:
@KatieWoe if you are finding the behavior is at odds with this, please let us know. |
No, it's behaving correctly. I just find the correct behavior odd. |
Actually, never mind. I think I do see something. |
Calling QA here |
Wonderful. Thanks so much for your work on this one QA team, it was a beast. |
RC Test
Mentions: @emily-phet @terracoda @BLFiedler @jessegreenberg
Simulation links
Test Matricies
Features included
Focus and Special Instructions
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=true
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
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:
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: