Dev Test: Number Play 1.1.0-dev.10

[chrisklus]

Dev Test

Mentions: @amanda-phet @zepumph @chrisklus @Nancy-Salpepi @kathy-phet @KatieWoe

This is the first dev test since 1.0 was published in spring of 2022, but please note that #917 has some overlap with Number Play. Thanks all!

Simulation links

• github repository for issues
• phet top-level directory
• sim: all_phet.html

Test Matrix

Please include all (non-screen reader) feature testing in these records if applicable.

• Latest macOS, Safari (Time = 3.5hrs)
• Windows 10, Chrome (Time = 1.5)
• Windows 10/11, Firefox (Time = 1.5)
• Latest iOS, Safari (Time = 3.5)
• Windows 11, Chrome (Time =4.5)

Light testing, or optionally skip if time crunch:

• Latest macOS, Chrome (Time =1.75hrs)
• Latest Chrome OS, Chrome (Time = 1hr)

Features included

• Speech Synthesis (not voicing, but still speaks to you).

Focus and Special Instructions

• Please test the locale settings and number speaking quite extensively, as we have made made changes here even since the number-compare dev.6 dev test.
• Please note that there are lots of great cases and examples of imperfection with ordering, layering, and hiding objects especially on the lab screen. Feel free to make GitHub issues for this kind of thing, but please don't spend an exorbitant amount of time here, as there is a good chance that, unless it poses serious concern pedagogically, that we do not have the bandwidth to fix it.
• The Lab screen is the exact same code as Number Compare except that this Lab screen doesn't have compare symbol cards.
• The Game screen has not changed much since 1.0 - the main change is that there is a reward node now.

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.

• On Chromebook, it sometimes takes two actions before a statement is heard number-compare#32

---

For QA...

General features

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.

---

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:

  • Alternative Input
  • Interactive Description
  • Sound and Sonification
  • Pan and Zoom
  • Mobile Description
  • Voicing

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

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:

  <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]

Calling testing here

[chrisklus]

Thanks you all!! I'm going to go ahead and close.