-
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: Faraday's Electromagnetic Lab 1.0.0-rc.1 #1116
Labels
Comments
github-project-automation
bot
moved this to Upcoming Tests (by priority)
in QA Pipeline
Jul 18, 2024
This was referenced Jul 18, 2024
KatieWoe
moved this from Upcoming Tests (by priority)
to Active Tests (max 5, by priority)
in QA Pipeline
Jul 22, 2024
Since we'll need an RC spot-check for phetsims/faradays-electromagnetic-lab#194... Yes, please do create an issue for the overlapping pointer areas. |
This was referenced Jul 25, 2024
QA is done |
KatieWoe
moved this from Active Tests (max 5, by priority)
to Dev & RC: ready for next steps
in QA Pipeline
Jul 26, 2024
Thanks QA! All issues have been addressed, so proceeding with 1.0.0-rc.2 spot check. |
github-project-automation
bot
moved this from Dev & RC: ready for next steps
to Done
in QA Pipeline
Jul 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RC Test
Mentions: @arouinfar @ariel-phet @kathy-phet @KatieWoe @Nancy-Salpepi
Simulation links
Test Matrices
Features included
SonificationDescriptionVoicingFocus and Special Instructions
Be on the lookout for common-code regressions, related to changes announced recently in the Slack#quality-assurance channel.
This sim is part of a suite of 4 sims, all being released and tested at the same time. Faraday's Electromagnetic Lab is the full sim, and should therefore receive a full RC test. The other sims are derivates, and require only an RC spot-check.
The QA issues for the other sims in this suite are:
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
See QA Book for a list of query parameters.)
spreadsheet and notify AR or AM if it not there.
is a problem.
add a comment in the RC test issue indicating so. If not, please open a new issue and specify what changes should be
made.
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: