Dev test: Masses And Springs Basics 1.0.0-dev.11

[Denz1994]

Masses-And-Springs-Basics is ready for the first round of dev testing. This dev test should foucus on catching bugs and any sim breaking behavior. This is a Phet brand sim and isn't instrumented for Phet-IO. Please report any bugs to https://github.com/phetsims/masses-and-springs-basics/issues.

Thanks, @ariel-phet and @arouinfar for the design input. Tagging @ariel-phet to mark priority or add further input.

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.

General Dev Test Platforms

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

Issues to Verify

• Please determine if ghost images of sliders are present on platforms/browsers related to Ghost image of slider masses-and-springs#334

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)

• Masses and Springs Basics

---

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.

---

[ariel-phet]

@KatieWoe #218 is a bit high priority to test than this sim, but this test should still be fairly high in the queue

[KatieWoe]

@Denz1994 the reset all pointer area may need another look. See https://github.com/phetsims/friction/issues/65

[Denz1994]

Opening a new issue related to #220 (comment).

[KatieWoe]

Major browsers tested. I'd like to keep this open a bit longer to see if we find anything new, but it looks like most major bugs have been found. Lowering priority.

[KatieWoe]

Didn't see phetsims/masses-and-springs#334 while testing. QA is done.

[Denz1994]

All sim related issues have been addressed. Related issues are either closed, fixed-awaiting-deploy for MAS maintenance release, or require verification in the next dev test. I'll close this issue and open a new issue for a second round of dev testing.