Dev Test: friction 1.6.0-dev.19

[zepumph]

@Matthew-Moore240 @terracoda @emily-phet @jessegreenberg, friction 1.6.0-dev.18 is ready for dev testing.
The goal of this test is to hammer out the inclusive feature-set and get that ready for publication, but we will not proceed with publication until PhET-iO instrumentation is complete (a couple of weeks away at least). Document issues in https://github.com/phetsims/friction/issues and link to this
issue. Please begin testing right away.

Assigning @kathy-phet and @KatieWoe for prioritization.

General Dev Test

What to Test

• Click every single button.
• 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.
• Try to include browser version numbers
• If there is a console available, check for errors and include them in the Problem Description.
• Run through the string tests on at least one platform, especially if it is about to go to rc.
• Check the Game Up harness on one platform.

Focus and Special Instructions

[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested,
list them here. Any behaviors you want QA to pay special attention to should be listed here.]

General Dev Test Platforms

• Latest macOS, Safari (Time =3.5 hr)
• Windows 10, Chrome (Time = 3 hr )
• Windows 10, Firefox (Time = 2.5 hr)
• Latest iOS, Safari (Time = 2.75 hr)

Light testing, or optionally skip if time crunch:

• Latest macOS, Chrome (Time = 1.5 hr)
• Latest Chrome OS, Chrome (Time =1.5 hr )

Issues to Verify

• iPad Reset Freeze (confirm you can't reproduce just like me)

These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for
QA then close the issue if fixed. If ready for review then leave open and assign back to the developer.

Link(s)

• Simulation

---

Accessibility (a11y) Dev Test

What to Test

• Specific instructions can be found below.
• Make sure the accessibility-related feature that is being tested doesn't negatively affect the sim in any way. Here is a list of features to supported in this test:
  • Alternative Input
  • Interactive Description
  • Sound and Sonification
  • Pan and Zoom
  • Voicing
• Load the a11y view and make sure that interacting with all elements in the simulation updates the appropriate descriptions in the PDOM.

Focus and Special Instructions

[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested,
list them here. Any behaviors you want QA to pay special attention to should be listed here.]

Link(s)

• a11y View
• Simulation

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) Not supported

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

• 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.

---

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]

QA is done

[zepumph]

Excellent! Thank you @KatieWoe and all QA.