RC test: pH Scale: Basics 1.5.0-rc.2

[pixelzoom]

@KatieWoe, @kathy-phet, @arouinfar, ph-scale-basics/1.5.0-rc.2 is ready for RC testing.

Since this sim is the first screen from ph-scale, please document issues in https://github.com/phetsims/ph-scale/issues and link to this issue.

This is a spot-check. There are no specific platforms that need specific testing.

Please test pH Scale 1.5.0-rc.2 before doing this issue. This sim is identical to the first screen in pH Scale, with one difference: the beaker does not automatically fill with solute when the sim starts. So after testing pH Scale 1.5.0-rc.2, you should be able to move quickly through this RC.

Assigning to @kathy-phet and @KatieWoe 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.

Issues to Verify

• update credits for 1.5.0 release ph-scale#155

These issues 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.

Link(s)

• Simulation
• iFrame
• XHTML
• Test Matrix

---

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.
• 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.
• If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
• Test that the sim works offline:
  • Go to https://phet-dev.colorado.edu/html/ph-scale-basics/1.5.0-rc.2/phet-io/ph-scale-basics-phet-io-1.5.0-rc.2.zip
  • download it
  • unzip it to a spot locally
  • Open index.html by double clicking it on your desktop or in a finder-view.
  • It should look like the standalone version of the sim in PhET-iO brand.

Issues to Verify

• Studio doesn't "Preview Sim" properly when solute is not at half a liter ph-scale#223

These issues 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.

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.

---

[KatieWoe]

QA is done

[pixelzoom]

Thanks @KatieWoe and QA team. 2 issues were verified, 0 failed. So ph-scale-basics is ready for publication.

Note that phetsims/ph-scale#225 is still a problem for ph-scale, but involves a screen that does not appear in ph-scale-basics, and ph-scale will require an additional RC. It would be wise to publish ph-scale and ph-scale-basics at the same time. So I'm going to wait to publish ph-scale-basics, and keep this issue open until then.

[pixelzoom]

ph-scale-basics will require another RC, due to phetsims/ph-scale#232.

[pixelzoom]

phetsims/ph-scale#232 was closed as "won't fix", so another RC is not necessary. Closing this issue, and proceeding with production publication.