Dev Test: Collision Lab 1.1.0-dev.2

[brandonLi8]

@arouinfar @ariel-phet, collision-lab/1.1.0-dev.2 is ready for dev testing. The intention is for this to be a quicker dev test administered by @arouinfar @ariel-phet before rc testing begins.

Document issues in https://github.com/phetsims/collision-lab/issues and link to this issue.

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.

Focus

1. Glaring performance issues/

2. Inelastic collisions! (things like phetsims/collision-lab#150, phetsims/collision-lab#139, phetsims/collision-lab#132, etc)

General Dev Test Platforms

• Latest macOS, Chrome and Safari
• Latest iOS, Safari
• Windows 10, all browsers (IE dropped)
• Latest Chrome OS, Chrome

Link(s)

• Simulation

---

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.

---

[arouinfar]

@brandonLi8 I've tested this quite a bit on latest macOS/Chrome and I'm not seeing any physics issues.

I plan on doing a bit more testing on macOS/Safari tomorrow.

[arouinfar]

macOS/Safari looked good to me. I did find one non-platform specific bug (phetsims/collision-lab#167) and suggested a small pixel polish (phetsims/collision-lab#168).

[ariel-phet]

Closing this dev test - @jonathanolson has made several improvements to the performance of the sim and we should test the latest version when available.