RC test: States of Matter: Basics 1.2.0-rc.1

[jbphet]

@KatieWoe , @ariel-phet, @arouinfar, and @kathy-phet - states-of-matter-basics/1.2.0-rc.1 is ready for RC testing. This includes both phet and phet-io brand and intended to be shared with a client in mid-August. Document issues in https://github.com/phetsims/states-of-matter-basics/issues and link to this issue.

Since this sim is a subset of states-of-matter, and states-of-matter is also being released at this time, it would probably be best to thoroughly test states-of-matter, and then do a more basic test on this one.

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

Since the phet-io version is being shared with a client who intends to integrate it into a learning environment, the phet-io version should be thoroughly tested. Also, lots of under-the-hood changes have occurred, so the phet version should get a fair amount of scrutiny too.

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.
• 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.

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

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 high priority but after #525 since this is a subset of that test.

[jbphet]

I'm going to close this, since I'm about to publish SOM 1.2.0-rc.2, and it would be better to roll a new release of SOMB as well so that SOM and SOMB are using as much of the same code as possible.