Skip to content
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: Ratio and Proportion 1.0.0-rc.1 #601

Closed
6 of 7 tasks
zepumph opened this issue Jan 27, 2021 · 6 comments
Closed
6 of 7 tasks

RC Test: Ratio and Proportion 1.0.0-rc.1 #601

zepumph opened this issue Jan 27, 2021 · 6 comments

Comments

@zepumph
Copy link
Member

zepumph commented Jan 27, 2021

@terracoda, @emily-phet, @BLFiedler, @Matthew-Moore240, @jessegreenberg, @jbphet, @Ashton-Morris, ratio-and-proportion/1.0.0-rc.1 is ready for RC testing.

This is the first publication for this brand new simulation. Ratio and Proportion supports the following accessibility features:

  • Alternative input and keyboard navigation
  • Sound
  • Interactive Description
  • Mobile Accessibility
  • Pan and Zoom

Document issues in https://github.com/phetsims/ratio-and-proportion/issues and link to this
issue.

Assigning to @kathy-phet and @KatieWoe for prioritization.

General RC Test

What to Test

  • Click every single button.
  • Test all possible forms of input.
    • Test all mouse/trackpad inputs.
    • Test all touchscreen inputs.
  • 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.
  • Test all query parameters on all platforms. (See QA Book
    for a list of query parameters.)
  • Download HTML on Chrome and iOS.
  • Make sure the iFrame version of the simulation is working as intended on all platforms.
  • Make sure the XHTML version of the simulation is working as intended on all platforms.
  • Complete the test matrix.
  • Don't forget to make sure the sim works with Legends of Learning.
  • Test the Game Up harness on at least one platform.
  • Check this LoL
    spreadsheet and notify AR or AM if it not there.
  • If this is rc.1 please do a memory test. (see Memory test: phet brand ratio-and-proportion#269)
  • When making an issue, check to see if it was in a previously published version
  • Try to include version numbers for browsers
  • If there is a console available, check for errors and include them in the Problem Description.
  • As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if
    there is a problem.
  • UPDATE: Please pay specific attention to hover highlighting behavior, both for mouse and (if applicable) touch.

Issues to Verify

Although this is the first RC, there are a couple of issues to be verified from previous testing.

These issues should have the "status:ready-for-qa" label. Check these issues off and close them if they are fixed.
Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. If the label is
"status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

Link(s)


Accessibility (a11y) RC Test

What to Test

  • Specific instructions can be found below.
  • Make sure the a11y feature doesn't negatively affect the sim in any way.
  • Test all possible forms of input.
    • Test all mouse/trackpad inputs.
    • Test all touchscreen inputs.
    • Test all keyboard navigation inputs.
    • Test all forms of input with a screen reader.
    • Test blended input using mouse/touch and keyboard.

Link(s)

Screen Readers

This sim supports 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
this Google Document. 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.

Final Requests


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:

  1. Consult the QA Book.
  2. Google it.
  3. Ask Katie.
  4. Ask a developer.
  5. Google it again.
  6. Cry.


@KatieWoe
Copy link
Contributor

KatieWoe commented Feb 3, 2021

Memory test results:
memtest

@KatieWoe
Copy link
Contributor

KatieWoe commented Feb 7, 2021

QA is done. Jaws was more partially tested due to phetsims/ratio-and-proportion#348, but I believe @loganbraywork spent some time on it as well.

@KatieWoe KatieWoe assigned zepumph and unassigned KatieWoe Feb 7, 2021
@Ashton-Morris
Copy link

There is no UI sound for checking or unchecking the "Enhanced Sound" option in the lower right speech bubble menu.
Since Enhanced Sound would be used for a population where sound was important I think we should add a UI sound.

I suggest using the standard Checkbox and UncheckBox sounds which is the sound used for the "Lock Ratio" option.

@emily-phet
Copy link

@Ashton-Morris nice catch!

After this initial publication, there will be a following publication that will move the "enhanced sound" option into the new Preferences menu Jesse is building. Let's not add sound to the current "enhanced sound" selection, but consider sound for the Preferences and Quick Menus. We might have a working version of this to demo for this Tuesday's sound meeting, and I can show you the latest then.

@jessegreenberg
Copy link
Contributor

@zepumph @KatieWoe ratio-and-porportion 1.0 scenery SHA received a patch for phetsims/phet-android-app#155.

If possible, please verify this sim works well in the PhET Android app as part of the next RC test.

@zepumph
Copy link
Member Author

zepumph commented Feb 13, 2021

All is done here, I'll note #601 (comment) in the next RC issue, and make a new RC, see phetsims/ratio-and-proportion#337

@zepumph zepumph closed this as completed Feb 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

6 participants