RC test: Balancing Chemical Equations 1.2.0-rc.2

[pixelzoom]

@KatieWoe , @arouinfar, @ariel-phet, Balancing Chemical Equations 1.2.0-rc.2 is ready for RC testing.

This RC is for brand=phet only (no PhET-io, no a11y), and it will not be provided to a client. The deadline mentioned in phetsims/balancing-chemical-equations#130 is "March", presumably 2019.

There is no need to do a full test matrix for this RC. See the "Issues to Verify" section below.

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.

Focus and Special Instructions

According to phetsims/balancing-chemical-equations#130, the primary motivation for this release is ePub and LoL support. Secondary is to pick up general common-code enhancements, and sim-specific changes identified in "Issues to Verify".

Sim-specific query parameters can be found in BCEQueryParameters. playAll and showReward are both useful for testing.

Issues to Verify

• use AccordionBox
• Memory Leak
• Smile covers tools when strings are doubled
• AccordionBox title bars have a cursor but are not clickable when closed

There is no need to do a full test matrix for this RC. These issues are all platform-independent, so it's sufficient to test them on 1 or 2 platforms. Check these issues off and close them if they are fixed, noting the test platform in the issue. 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]

• Win 10 chrome Full
• Win 10 firefox
• Win 10 edge Full

---

• Mac 10.14 chrome
• Mac 10.14 firefox Full
• Mac 10.14 safari Full

---

• iOS 12 Full
• iOS 10

---

• Chrome OS

---

• Win 7 IE Full
• Win 7 chrome
• Mac 10.11 safari
• Mac 10.11 firefox

[pixelzoom]

@KatieWoe That's quite a few more platforms than are necessary to test these particular issues. But if you have the time, I'll defer to your decision.

[KatieWoe]

@pixelzoom If something with higher priority comes in the repo we'll cut it down. At the moment we have time. Thanks.

[KatieWoe]

@pixelzoom EFAC just came in to the repo. If you are satisfied with this level of testing, we can call this done. If you want any other platforms checked, let me know.

[pixelzoom]

Thanks @KatieWoe. Based on the platforms that you've tested, I'm comfortable with calling this "done" and moving forward. I'll proceed with publishing 1.2.0.