RC Test: Resistance in a Wire 1.6.0-rc.3

[jbphet]

@ariel-phet, @emily-phet, @terracoda, @KatieWoe - Resistance in a Wire 1.6.0-rc.3 is ready for RC testing. This release addresses the handful of issues found during the testing of 1.6.0-rc.1. The issues are listed below, and in my opinion it will be enough to verify them and to spot check the sim on a few key platforms, since the changes for this release were minimal.

Please document issues in https://github.com/phetsims/resistance-in-a-wire/issues and link to this issue.

Assigning @ariel-phet 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.
• Check this LoL spreadsheet and notify AR if it not there.

Focus and Special Instructions

Special focus should be given to accessibility features, such as screen reader behavior, sonification, and keyboard navigation.

Issues to Verify

• VoiceOver reads out multiple resistance values after sliders stop being adjusted
• Max width of keyboardNav dialog
• Sound blurs when dragging starts off of thumb

These issues should have the "status:fixed-pending-testing" label. Check these issues off and close them if they are fixed.

Link(s)

• Simulation
• iFrame
• XHTML
• Test Matrix
• Legends of Learning Harness

---

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 (if applicable).
  • Test all forms of input with a screen reader (if applicable).

Focus and Special Instructions

Sonification is brand new, so should be tested well. Screen reader support was tested on the 1.5 release branch, but never actually released, so it should be tested reasonably well too.

Link(s)

• a11y View
• Simulation
• Test Matrix

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

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.

---

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]

@ariel-phet for priority

[ariel-phet]

@KatieWoe top priority along with Friction

[KatieWoe]

• Win 10 chrome Full
• Win 10 firefox
• Win 10 edge Full

---

• Mac 10.14 chrome
• Mac 10.14 firefox Full
• Mac 10.14 safari Full

---

• iOS 12 Full
• iOS 10

---

• Chrome OS

---

• Win 7 IE Full
• Win 7 chrome
• Mac 10.11 safari
• Mac 10.11 firefox

[KatieWoe]

Screen Readers checked.

[KatieWoe]

QA is done

[jbphet]

Thanks @phetsims/quality-assurance. I'll follow up on the issues listed above individually. Closing.