RC test: ph-scale 1.3.0-rc.2

[pixelzoom]

@KatieWoe, @ariel-phet, @arouinfar, ph-scale/1.3.0-rc.2 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

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

Issues to Verify

• performance of "H3O+/OH- Ratio" has degraded
• Hand cursor when faucet shooter is disabled
• Clicking on listbox may activate dropper
• Can't drag dropper while it dispenses
• update credits for 1.3.0 release
• fix for query-string-machine localStorage issue
• verify patch for phet-ios-app#484

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.

---

[ghost]

QA is done.

[pixelzoom]

Thanks again QA.

Self assigning. We'll need one more quick RC test to verify phetsims/ph-scale#91 and phetsims/ph-scale#87.

[pixelzoom]

Next RC test started in #383. Closing this issue.