RC test for molecule-shapes-basics 1.2.0-rc.1

[jonathanolson]

@ariel-phet, molecule-shapes-basics/1.2.0-rc.1 is ready for RC testing. Document issues in https://github.com/phetsims/molecule-shapes/issues and link to this issue.

Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

• Click every single button.
• Test all possible forms of input.
  • Test all mouse/trackpad inputs.
  • Test all touchscreen inputs.
• 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.
• Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
• Download HTML on Chrome and iOS.
• Make sure the iFrame version of the simulation is working as intended on all platforms.
• Make sure the XHTML version of the simulation is working as intended on all platforms.
• Complete the test matrix.
• Don't forget to make sure the sim works with Legends of Learning.
• Check this LoL spreadsheet and notify AR if it not there.
• If this is rc.1 please do a memory test.

Focus and Special Instructions

[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested, list them here. Any behaviors you want QA to pay special attention to should be listed here.]

Issues to Verify

• Non-WebGL screenshot reversed

These issues should have the "status:fixed-pending-testing" label. Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed.

Link(s)

• Simulation
• iFrame
• XHTML
• Test Matrix
• Legends of Learning Harness

---

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.

---

[jonathanolson]

Main issue for creating this release: phetsims/molecule-shapes-basics#9

[ariel-phet]

@KatieWoe #277 and #278 should come first, but this sim we also want to republish before March, should be straightforward as just being republished off master.

[KatieWoe]

This looks like it may be a memory leak. @jonathanolson let me know if you want an issue for it.
Start: 59.5
1: 70.6
2: 72.8
3: 74.4
4: 75.8
5: 77.3
6: 78.9
7: 80.2
8: 81.4
9: 82.7
10: 84.0
20: 91.0
30: 98.9
40: 105

[ariel-phet]

moving to high priority in the queue

[KatieWoe]

QA is done. Since the app came out and that was the stated date for dropping iOS 9 (and 10 I believe) those two platforms were only tested for performance.

[jonathanolson]

This release branch had patches related to phetsims/chipper#720 and phetsims/brand#34 applied since the last RC. This sim should have another RC done, if only to test the brand-related changes briefly.

[jonathanolson]

Thanks for testing, I should have rc.2 momentarily.