RC test: pH Scale 1.4.0-rc.2

[pixelzoom]

@arouinfar phet-scale/1.4.0-rc.2 is ready for RC testing.

⚠️ Milestone for delivering 1.4.0 to the client is 9/1/2020.

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.
• Test the Game Up harness on at least one platform.
• 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
• Try to include version numbers for browsers
• If there is a console available, check for errors and include them in the Problem Description.
• As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if
  there is a problem.

Focus and Special Instructions

None of the "Issues to Verify" are platform specific. They can be spot-checked on a few platforms.

Issues to Verify

See the last comment in each issue for "how to test" instructions.

Sim-specific:

• update credits for 1.4.0 release
• Switching to empty beaker disables water faucet
• rename ?autoFill to ?autofill

Common Code:

• About dialog is scaled incorrectly
• problems with screens query parameter
• Incorrectly written scientific notation
• Faucet knobs don't have indicated pointer areas
• Long string is off center on home screen
• X button on dialog may have too small pointer area

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

---

PhET-iO RC 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.
• N/A For an update or maintenance release please check the backwards compatibility of the playback wrapper.
  Here's the link to the previous wrapper.
• Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:

  /wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER
  

  Further instructions in QA Book
• Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other random platform.
• Conduct a memory test on the stand alone sim wrapper (rc.1).
• Test one platform combination with ?phetioDebug on the Studio and State wrapper.

Focus and Special Instructions

None of the "Issues to Verify" are platform specific. They can be spot-checked on a few platforms.

Issues to Verify

See the last comment in each issue for "how to test" instructions.

• empty client guides published with this sim
• titleText.visibleProperty gets reset when you switch screens
• Studio search feature is broken
• empty Solute list box causes the sim to crash
• autofill still occurs with invisible dropper
• rename ?autoFill to ?autofill
• Tandem.REQUIRED is no longer checked
• 3rd Screen Ratio dots do not show up on launched sim
• Mirror wrapper may be unsynced during a slow load
• PhET-iO API error when using 'screens' query parameter
• Old search remains when reopening studio tab from history
• Add "Item" suffix to Solute combo box items

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)

• Wrapper Index
• Test Matrix

---

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.

---

[ariel-phet]

@KatieWoe currently a high priority given the timeline but only after #531 and #532 are complete

[pixelzoom]

@kathy-phet requested that this RC be canceled because https://github.com/phetsims/studio/issues/183 was discovered after publication, and it's a blocking issue.

Assigning this issue to me, to be used for the creation of the next RC issue.

[pixelzoom]

1.4 release branches have been abandoned, and the RC process will be restarted with a new release branch. See phetsims/ph-scale#166 (comment). Closing.