RC test: pH Scale: Basics 1.4.0-rc.1

[pixelzoom]

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

This RC test should be done at the same time as #514 (pH Scale 1.4.0-rc.1).

Document issues in https://github.com/phetsims/ph-scale/issues (NOT in ph-scale-basics) 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
• 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

These changes and fixes should be verified:

• order solutes alphabetically in combo box
• setting maxWidth for listboxParent causes scale/position problem

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. 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.
• 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
• Please at least load all wrappers except studio in the wrapper suite with internet explorer.

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.

---

[pixelzoom]

@ariel-phet @KatieWoe @arouinfar There are specific PhET-iO requirements for this sim (from PhET and a client), which should be verified by QA. I'm still unclear on how those requirements are to be communicated to QA for verification, so there's no information about this in the above issue template. You'll need to discuss how to proceed.

[arouinfar]

I've uploaded temporary pdf's to the phet-io-client-guides repo: https://github.com/phetsims/phet-io-client-guides/tree/master/ph-scale. The original documentation did not separate ph-scale and ph-scale-basics.

In the future, these will be md files that exist before a dev/rc/production version gets built and they will be linked to from the Wrapper Index Page.

@KatieWoe, the client-specific customization requests and the corresponding phetioIDs can be found in client-requests.pdf. The phet-io-guide.pdf includes information about simulation-specific query parameters that might be useful for testing.

[ariel-phet]

@KatieWoe top priority (#513 comes first, but if it makes sense to do testing of this sim while on a specific platform along with MAL, testing priority can be considered concurrent).

[pixelzoom]

@kathy-phet said in 7/16/2020 phet-io meeting that the milestone for publishing 1.4.0 and delivering to the client is 9/1/2020.

[KatieWoe]

Phet-io Memory Test

[KatieWoe]

QA is done

[pixelzoom]

Thanks @KatieWoe and QA team.

Unfortunately, there were a lot of problems found with this RC -- mostly PhET-iO and common code. So this is going to require another RC test cycle. I'll leave this issue open until I've created the next RC and its associated QA issue.

EDIT: Currently blocked by phetsims/ph-scale#172.

[pixelzoom]

Here's what I need to copy to the next RC issue:

Issues to Verify (brand=phet)

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
• Faucet knobs don't have indicated pointer areas
• X button on dialog may have too small pointer area

Issues to Verify (brand=phet-io)

• empty client guides published with this sim
• 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
• Mirror wrapper may be unsynced during a slow load
• Old search remains when reopening studio tab from history
• Add "Item" suffix to Solute combo box items

[pixelzoom]

1.4.0-rc.2 has been published, tracking in #535.