Dev test: Molecule Shapes 1.5.0-dev.3

[jonathanolson]

@arouninfar, @kathy-phet, molecule-shapes/1.5.0-dev.3 is ready for dev testing. Document issues in https://github.com/phetsims/molecule-shapes/issues and link to this
issue.

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.

General Dev Test Platforms

• Latest macOS, Safari (Time = 2.25 hrs)
• Windows 10, Chrome (Time = 2.00 hrs )
• Windows 10, Firefox (Time = 1.5 hrs)
• Latest iOS, Safari (Time = 1.5)
• Win 11 Firefox (Time = 2)

Light testing, or optionally skip if time crunch:

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

Issues to Verify

• Many credits gone

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

---

PhET-iO Dev Test

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.

General Dev Test Platforms

• Latest macOS, Safari (Time = 2 hrs)
• Latest iOS, Safari (Time = 2)
• Windows 11, Chrome (Time = 3)
• Windows 10, Firefox (Time = 2 hrs)
• Latest Chrome OS, Chrome (Time = 2)

Link(s)

• Wrapper Index

---

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:

[KatieWoe]

QA is done

[jonathanolson]

Thanks!