Dev test: gravity-and-orbits/1.2.0-dev.10

[samreid]

@ariel-phet @KatieWoe @arouinfar, gravity-and-orbits/1.2.0-dev.10 is ready for dev testing. We had a milestone to release this to the client by May 22, as described in phetsims/gravity-and-orbits#315. Also, @kathy-phet recommended to test this after States of Matter testing is complete (which looks like it wrapped up last week).
Document issues in https://github.com/phetsims/gravity-and-orbits/issues and link to this issue.

Assigning @ariel-phet 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.

Focus and Special Instructions

Physics implementation and numerical constants have changed, please test accordingly.

General Dev Test Platforms

• Latest macOS, Chrome and Safari
• Latest iOS, Safari
• Windows 10, all browsers
• Latest Chrome OS, Chrome

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, all browsers
• Latest iOS, Safari
• Windows 10, all browsers, including IE
• Latest Chrome OS, Chrome

Focus and Special Instructions

Basic testing to make sure the client can achieve their customization goals for the PhET-iO version.

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 looks ok:

[ariel-phet]

Current top testing priority

[zepumph]

As part of this issue, can you please confirm that phetsims/states-of-matter#281 is fixed. That issue is not sim specific, and should be dealt with in this version of phet-io.

[KatieWoe]

ChromeOS seemed to be a bit slow generally. Particularly in Phet-io

[KatieWoe]

QA is done