RC test: ph-scale 1.3.0-rc.3

[pixelzoom]

@KatieWoe, @ariel-phet, @arouinfar, ph-scale/1.3.0-rc.3 is ready for RC testing. This is for brand=phet only. PhET-iO and a11y are not included.

Document issues in https://github.com/phetsims/ph-scale/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 or AM 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
• If there is a console available, check for errors and include them in the Problem Description.

Focus and Special Instructions

This is a spot check. A full test matrix is not necessary. Verify the issues in "Issues to Verify" on one or two platforms.

Issues to Verify

• update credits for 1.3.0 release
• Interrupting initial filling of bucket

These issues should have the "status:ready-for-qa" 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 and link back to this issue. If the label is "status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if 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.

---

[KatieWoe]

• Win 10 chrome
• Win 10 firefox
• Win 10 edge

---

• Mac 10.14 chrome
• Mac 10.14 safari

---

• Win 7 IE
• Mac 10.11 safari

---

• ChromeOS
• iOS 12

---

@pixelzoom to approve test devices

[pixelzoom]

That's definitely overkill for #383 (credits). One platform is sufficient.

I think it's also a bit much for phetsims/ph-scale#87, but probably a good idea.

[KatieWoe]

QA is done

[pixelzoom]

Thank you QA. This concludes the RC process. Production version 1.0.0 has been deployed. Closing.