RC test: Masses and Springs Basics 1.0.0-rc.3

[Denz1994]

@ariel-phet , @arouinfar , Masses-and-Springs-Basics/1.0.0-rc.3 is ready for RC testing. Document issues in https://github.com/phetsims/Masses-and-Springs-Basics/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.
• When making an issue, check to see if it was in a previously published version

Issues to Verify

• GravityAccordionBox requires model
  -Please toggle through gravity settings to ensure sim isn't crashing.
• Gravity maxWidth is too small
• [Lab Screen] Movable Line position doesn't reset on ResetAll
• Pointer Area Overlap of mass adjuster
• Short Strings are centered
• Period Trace stops after it is complete when stepping through animation
• [Stretch Screen] ruler returns home when window dimensions change
• Add Credits

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]

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.

[KatieWoe]

QA is done

[Denz1994]

Once brands-related changes are completed from #296 (comment), a new issue will be created in QA and that should be the last item to test for MASB before a production version. The changes ensure that older versions of sims are compatible with phetmarks.

[Denz1994]

@jonathanolson This sim had changes related to phetsims/brand#34 already included in the latest RC. See this commit.

Siding with your comment here, we shouldn't need QA to verify.

[Denz1994]

phetsims/masses-and-springs-basics#31 was the last issue to verify. RC testing has concluded. Closing.

Thanks QA!