Dev Test: Models of the Hydrogen Atom 1.0.0-dev.29

[pixelzoom]

Dev Test

Mentions: @arouinfar @Nancy-Salpepi @DianaTavares @KatieWoe @kathy-phet

Simulation links

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

Test Matrix

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

• Latest macOS, Safari (Time = 2) (Tester = NS)
• Latest iOS, Safari (Time = 1.5) (Tester = AM)
• Windows 10/11, Firefox (Time = 2) (Tester = MM)
• Windows 11, Chrome (Time = 2) (Tester = KW)
• Latest Chrome OS, Chrome (Time = .5) (Tester = KW)

Light testing, or optionally skip if time crunch:

• Latest macOS, Chrome (Time = ) (Tester = )
• Windows 10, Chrome (Time = ) (Tester = )

If PhET-iO is being tested:

• Latest macOS, Safari (Time = 2) (Tester = NS)
• Windows 10, Chrome (Time = 1.5) (Tester = NS)
• Windows 10/11, Firefox (Time = 1.5) (Tester = MM)
• Latest iOS, Safari (Time = .75) (Tester = NS)
• Windows 11, Chrome (Time = 2) (Tester = KW)

If screen readers are being tested:

• Win 10/11 Chrome + Jaws (Time = .5) (Tester = KW)
• Win 10/11 Firefox + NVDA (Time = .5) (Tester = KW)
• MacOS Safari + VO (Time = .75) (Tester = NS)
• iPadOS Mobile VO (Time = 1) (Tester = NS)

Features included

• PhET-iO
• Dynamic Locale
• Alternative Input
• UI Sound
• Sonification
• Description (Tier 1)
• Voicing

Focus and Special Instructions

Please do a memory test, and record results in phetsims/models-of-the-hydrogen-atom#120.

Please include performance testing on Chromebook and iPad, and record results in phetsims/models-of-the-hydrogen-atom#121.

This is a 1.0 release, and there is no prior PhET-iO release. Comparison with previous versions is irrelevant.

Tier 1 Description is included, and should be tested in the A11y View and with a screen reader. This includes accessible name, accessible helptext, and static screen summary.

Issues to Verify

These issues have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.

• Memory testing. models-of-the-hydrogen-atom#120
• Performance sign-off. models-of-the-hydrogen-atom#121
• Credits for 1.0 release models-of-the-hydrogen-atom#23

---

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.

---

PhET-iO features

What to Test

• Make sure that public files do not have password protection. Use a private browser for this.
• Make sure that private files do have password protection. Use a private browser for this.
• Make sure standalone sim is working properly.
• Make sure the wrapper index is working properly.
• Make sure each wrapper is working properly.
• Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
• For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
  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:

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

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

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

  <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