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

[samreid]

@ariel-phet circuit-construction-kit-dc/1.1.0-dev.3 is ready for dev testing. @kathy-phet wants to share this with a client around the end of April. Please document issues in https://github.com/phetsims/circuit-construction-kit-common/issues and link to
this issue.

Assigning @ariel-phet for prioritization, and to update the General Dev Test Platforms list.
@ariel-phet, do you want any others issues addressed or features added before proceeding with dev test? Please also look through this template and update anything you can see that needs to be updated, and please label accordingly.

General Dev Test

What to Test

• Click every single button.
• Make sure you can't lose anything.
• Play with the sim normally.
• Try to break the sim.

Focus and Special Instructions

The new component is the Fuse, which appears on the 2nd page of the carousel. The fuse should be thoroughly tested,
but the rest of the sim needs to be tested as well to make sure nothing was broken during the last several months.

General Dev Test Platforms

• Latest macOS, Chrome and Safari
• Latest iOS, Safari
• Windows 10, all browsers
• Latest Chrome OS, Chrome

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

---

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 testing priority

[KatieWoe]

QA is done with the dev test.

[KatieWoe]

#314 is out so I'm closing this.