Dev Test: Molecule Shapes 1.5.0-dev.4

[jonathanolson]

Dev Test

Mentions: @arouinfar @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 = 2hrs)
• Windows 10, Chrome (Time = 1hr)
• Windows 10/11, Firefox (Time = 2)
• Latest iOS, Safari (Time = .5)
• Windows 11, Chrome (Time = 1.5)

Light testing, or optionally skip if time crunch:

• Latest macOS, Chrome (Time = .75hr)
• Latest Chrome OS, Chrome (Time = )

If PhET-iO is being tested:

• Latest macOS, Safari (Time = 3.5hrs)
• Windows 10, Chrome (Time =2hrs)
• Windows 10, Firefox (Time = 2.5)
• Latest iOS, Safari (Time = .25)
• Windows 11, Chrome (Time = 2.5)

Features included

• PhET-iO
• Alternative Input
• UI Sound
• Sonification
• Description
• Voicing

Focus and Special Instructions

The focus of testing should be on the PhET-iO feature set. In particular:

• Read through the PhET-iO Guide and Examples docs linked on the wrapper index page. Verify that the links are working. Attempt the customizations outlined in both docs, especially those related to new features (customizing strings & locales, preferences, screens, and using Get Value/Set Value). Note that there are still a few remaining TODOs in the PhET-iO Guide which are documented in the Documentation/Communication column in https://github.com/orgs/phetsims/projects/44.
• There are a few known issues that have been tagged below. No need to focus on these bugs, but feel free to add additional information if you discover anything during testing.
• This will be the first version of PhET-iO available to clients (previous version was for a research partner), so no need to test migration.
• If anything looks amiss, check the issues in https://github.com/orgs/phetsims/projects/44 for a paper trail.

---

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]

Memory Test:

PhET-iO Memory Test:

[Nancy-Salpepi]

@arouinfar @jonathanolson
Noting that the bond angle border looks lighter in screenshots for the full and basics versions. Seen on Mac + safari/chrome. Let me know if it warrants an issue.

[arouinfar]

Noting that the bond angle border looks lighter in screenshots for the full and basics versions. Seen on Mac + safari/chrome. Let me know if it warrants an issue.

The difference looks pretty minor to me. Best guess is that there was a scenery change sometime between the creation of the 1.2 branch (early 2019) and now that could explain this difference. I don't think it warrants an issue, though.

[KatieWoe]

Calling QA here

[KatieWoe]

This is in rc. Closing