RC test: Molecule Shapes: Basics 1.2.0-rc.2

[jonathanolson]

@ariel-phet, @kathy-phet, @amanda-phet molecule-shapes-basics/1.2.0-rc.2 is ready for RC testing. April 1st deadline, see https://github.com/phetsims/special-ops/issues/132. Document issues in https://github.com/phetsims/molecule-shapes/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 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

Issues to Verify

• Molecule in screen selection and boded atoms in model screen disappears
• Color of Br is incorrect
• Molecules can change other molecule's orientation
• Win 10 Firefox Model Screen blank
• Projector Mode max width short
• Red X appears on bond atoms not present upon load
• Low graphics warning

These issues should have the "status:fixed-pending-testing" 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.

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.

---

[KatieWoe]

Per @kathy-phet this will be much closer to a spot check due to time constraints.

[KatieWoe]

I'm going to call this for now so that @jonathanolson has a chance to fix anything and get it confirmed. String tests, iframe, xhtml, and LoL only tested on one platform. All other platforms tested for usability and screenshots. See Testing Matrix for specific tests done.

[jonathanolson]

Thanks! The issues should be fixed in #305.