Dev test: Circuit Construction Kit: DC 1.1.0-dev.7

[samreid]

@ariel-phet, circuit-construction-kit-dc/1.1.0-dev.7 is ready for dev testing. I'm not certain about deadlines. Document issues in https://github.com/phetsims/circuit-construction-kit-common/issues and link to this issue. I expect we will want to test "DC: Virtual Lab" at the same time, so I have published a dev version and linked it below. @ariel-phet please correct me if it should not be tested now, or if it should have a separate issue.

Assigning @ariel-phet for prioritization.

General Dev Test

What to Test

• Click every single button.
• 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.

Focus and Special Instructions

Prior dev testing was completed in #311. Since then, we've also worked on:

• Improvements for hit areas for the accordion box button, see Pointer Areas hard to hit circuit-construction-kit-common#491
• Improved readout for the fuse values: Include internal resistance in fuse model? circuit-construction-kit-common#480
• Reversing the red/black probes on the voltmeter, see Proposal to switch red/black leads on volt meter circuit-construction-kit-common#482

@ariel-phet requested a "sanity" dev test one one or two platforms before RC (like chrome and iPad)".

For each discovered issue, please compare to the published version and report whether the problem is new or pre-existing in the published version.

General Dev Test Platforms

• Latest Chrome on Win
• Latest iOS, Mobile Safari

Link(s)

• CCK:DC
• CCK-DC-virtual lab

---

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]

Current top priority

[ariel-phet]

And yes, @samreid makes sense to publish both

[KatieWoe]

QA is done.

[samreid]

Thanks @KatieWoe! All issues tracked elsewhere, closing.