Dev test: Energy Skate Park 1.0.0-dev.4

[jessegreenberg]

@arouinfar, @ariel-phet energy-skate-park/1.0.0-dev.4 is ready for dev testing. This is the first dev test of energy-skate-park, although the sim is quite similar to energy-skate-park-basics. The largest changes from the basics version are that you can record skater data (Measure screen and Graphs screens) play back skater states from graphs (Graphs screen), as well as change gravity and skater mass. Please test these new features thoroughly in particular. It would also be helpful to get a sense of sim performance, please test this sim on an array of slow platforms and report results. Finally, document any issues in https://github.com/phetsims/energy-skate-park/issues and link to this issue. Thanks!

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.
• If there is a console available, check for errors and include them in the Problem Description.
• Rung through the string tests on at least one platform, especially if it is about to go to rc.

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.]

General Dev Test Platforms

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

These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for QA then close the issue if fixed. If ready for review then leave open and assign back to the developer.

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]

Exciting to see this going up for a dev test!

@jessegreenberg @ariel-phet @KatieWoe I need to focus on the upcoming workshop I'll be giving in Peru 8/16. I likely won't be very responsive on GitHub for the next two weeks, but if anything blocking comes up, please let me know.

[KatieWoe]

Seeing phetsims/energy-skate-park-basics#440 here too. I'm guessing it should be deffered as well. @ariel-phet @jessegreenberg let me know if you want a new issue for this.

[KatieWoe]

QA is done

[jessegreenberg]

Awesome, thank you for the testing @KatieWoe and team. In the original ticket

It would also be helpful to get a sense of sim performance, please test this sim on an array of slow platforms and report results.

I didn't see anything mentioned so just checking in, did you notice any performance issues on slow platforms @KatieWoe?

[KatieWoe]

Sorry, I missed that. I'm going to do a quick second check.

[KatieWoe]

Looks acceptable on IE, iOS 9 and iOS 10

[jessegreenberg]

OK, that is great to hear @KatieWoe. Thank you for checking.