RC Test: circuit-construction-kit-dc/1.1.0-rc.1 and circuit-construction-kit-dc-virtual-lab/1.1.0-rc.1

[samreid]

@ariel-phet, @KatieWoe, @arouinfar & @kathy-phet circuit-construction-kit-dc/1.1.0-rc.1 and
circuit-construction-kit-dc-virtual-lab/1.1.0-rc.1 are ready for RC testing. A recent dev version has already been shared with a client, and I'm not sure of the priority for this version. Please document issues in https://github.com/phetsims/circuit-construction-kit-common/issues and link to this issue.

Prior dev testing was recently completed in #361

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

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

• Simulation VL

• iFrame VL

• XHTML VL

• Test Matrix VL

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

---

[samreid]

This RC is likely affected by https://github.com/phetsims/phet-android-app/issues/71

UPDATE: RC is probably not affected by that problem since it was published after fixes in QueryStringMachine.

[ariel-phet]

Putting at medium for the moment since some other very high priority issues currently in the queue

[KatieWoe]

QA is done

[KatieWoe]

Wait, let me do a quick memory check

[KatieWoe]

CCK Results:

[KatieWoe]

VL Results:

[KatieWoe]

Memory results jump around and can get rather large, but it doesn't seem to be growing so I'm not too worried. QA is done.

[samreid]

Thanks, I'll deploy as part of phetsims/circuit-construction-kit-common#500, closing.