Dev test: Energy Forms and Changes 1.2.0-dev.12

[chrisklus]

@KatieWoe, @arouinfar, @kathy-phet, energy-forms-and-changes/1.2.0-dev.12 is ready for dev testing. Once published, the phet-io brand version of this sim will be shared with a client, and phet brand will be the latest release for the website. Please document issues in https://github.com/phetsims/energy-forms-and-changes/issues and link to this issue.

I kept the phet brand section, but since QA just did a dev test for phet brand, I think it's reasonable to focus on phet-io brand for this dev test and then test both brands equally again for the first RC. Anyone please speak up if you disagree.

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.

General Dev Test Platforms

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

Link(s)

• Simulation

---

PhET-iO Dev Test

What to Test

• Make sure that public files do not have password protection. Use a private browser for this.
• Make sure that private files do have password protection. Use a private browser for this.
• Make sure standalone sim is working properly.
• Make sure the wrapper index is working properly.
• Make sure each wrapper is working properly.
• Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
• For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make sure the simulation loads without crashing or throwing errors.

General Dev Test Platforms

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

Focus and Special Instructions

Please thoroughly test state for both screens. Note that this might be easiest to do by configuring a state in Studio and then hitting "launch". If you prefer to use the state wrapper for testing state, you'll need to increase numberOfMillisecondsBetweenUpdates to a point where the sim is usable for you. At the default value of 1000 ms, the sim is very laggy because setting state alone takes about a second in this sim. The issue below identifies some items to look out for on the second screen.

Issues to Verify

• State

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)

• Wrapper Index

---

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.

---

[KatieWoe]

Recommend closing this since rcs are coming up.