-
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
Dev-Lite Test: Density (1.2.0-dev.2) + Buoyancy (1.0.0-dev.9) + Buoyancy: Basics (1.0.0-dev.5) #1095
Closed
13 of 17 tasks
Labels
QA:dev-lite
Early, short dev test
Comments
1 task
This was referenced Jun 12, 2024
samreid
changed the title
Dev-Lite Test: Density (1.2.0-dev.1) + Buoyancy (1.0.0-dev.9) + Buoyancy: Basics (1.0.0-dev.5)
Dev-Lite Test: Density (1.2.0-dev.2) + Buoyancy (1.0.0-dev.9) + Buoyancy: Basics (1.0.0-dev.5)
Jun 12, 2024
This was referenced Jun 12, 2024
Closed
This was referenced Jun 13, 2024
This was referenced Jun 14, 2024
This was referenced Jun 17, 2024
QA is done |
Thank you so very much QA. This was an impressive haul of issues you found. This will jumpstart our refinement period immensely. We appreciate you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dev-Lite Test
Mentions: @DianaTavares @AgustinVallejo @zepumph @samreid @kathy-phet @KatieWoe @Nancy-Salpepi
Simulation links
For Density:
For Buoyancy:
For Buoyancy Basics:
Test Matrix
Density/PhET-iO:
Buoyancy:
Buoyancy PhET-iO:
Buoyancy Basics/PhET-iO:
Features included
SonificationDescriptionVoicingFocus and Special Instructions
This is a first initial dev-lite test for Density, Buoyancy, and Buoyancy: Basics. Density was previously published
but is somewhat older and has undergone numerous changes, so needs to be retested. Please look for any buggy behavior
in the model or views. If the desirable behavior is unclear, please reach out to @DianaTavares
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
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: