Dev Test: Circuit Construction Kit DC 1.4.0-dev.2

[zepumph]

Dev Test

Mentions: @matthew-blackman @samreid @arouinfar

Simulation links

• github repository for issues
• phet top-level directory
• sim: all_phet.html
• phet-io wrapper index

Test Matrix

Please include all (non-screen reader) feature testing in these records if applicable.

• Latest macOS, Safari (Time = .5 ) (Tester = NS)
• Latest iOS, Safari (Time = .5) (Tester = NS)
• Windows 10/11, Firefox (Time = .5) (Tester = MM)
• Windows 11, Chrome (Time = .5) (Tester = KW)
• Latest Chrome OS, Chrome (Time = .5) (Tester = MM)

Light testing, or optionally skip if time crunch:

• Latest macOS, Chrome (Time = ) (Tester = )
• Windows 10, Chrome (Time = ) (Tester = )

If PhET-iO is being tested:

• Latest macOS, Safari (Time = 2) (Tester = NS)
• Windows 10, Chrome (Time = ) (Tester = )
• Windows 10, Firefox (Time = 2) (Tester = MM)
• Latest iOS, Safari (Time = 1) (Tester = NS)
• Windows 11, Chrome (Time = 2) (Tester = KW)

Features included

• PhET-iO
• Dynamic Locale
• Alternative Input
• UI Sound
• Sonification
• Description
• Voicing

Focus and Special Instructions

NOTE: This sim just went through a dev test on main: #1217

• (1) There is no need to repeat much of the testing that occurred during that test, but it didn't seem like that dev test outlined all of this sim's featureset (phet-io, dynamic locale). Please give those features full attention, as well as due diligence on testing that was done and finished last Friday. Sorry for the trouble, and thanks for your patience!

• (2) When you are ready for dev versions, I will also make a dev version of cck-dc-virtual. DO NOT DO FULL DEV TESTING ON VIRTUAL LAB. The only difference between it and the full dc version is one hidden component. That said, at the end of this dev test, please give 15 minutes of testing on one device to the following links:

  • virtual lab sim: all_phet.html
  • virtual lab studio

• (3) Please do migration testing for both sims, but focus 90% of your time on cck-dc:

  • dc migration
  • virtual lab migration

And, as always. Thank you!!!

Issues to Verify

These issues should have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer. Please close once confirmed fixed

• Keyboard navigation appears to be broken and creates a focus trap for any surrounding content circuit-construction-kit-dc#209 (comment)
• Clicking away from a highlighted circuit component doesn't always unhighlight that component circuit-construction-kit-common#1023 (comment) (this has already been verified, but please give it another 30 seconds to confirm fixed, and with phet-io brand).

---

For QA...

General features

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.
• Try to include browser version numbers
• If there is a console available, check for errors and include them in the Problem Description.
• Run through the string tests on at least one platform, especially if it is about to go to rc.
• Check the Game Up harness on one platform.

---

PhET-iO features

What to Test

• Make sure that public files do not have password protection. Use a private browser for this.
• Make sure that private files do have password protection. Use a private browser for this.
• Make sure standalone sim is working properly.
• Make sure the wrapper index is working properly.
• Make sure each wrapper is working properly.
• Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
• For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
  sure the simulation loads without crashing or throwing errors.

---

Accessibility features

What to Test

• Specific instructions can be found above.

• Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
  a list of features that may be supported in this test:

  • Alternative Input
  • Interactive Description
  • Sound and Sonification
  • Pan and Zoom
  • Mobile Description
  • Voicing

• Test all possible forms of input.

  • Test all mouse/trackpad inputs.
  • Test all touchscreen inputs.
  • Test all keyboard navigation inputs (if applicable).
  • Test all forms of input with a screen reader (if applicable).

Screen Readers

This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

• Windows 10 + Latest Chrome + Latest JAWS
• Windows 10 + Latest Firefox + Latest NVDA
• macOS + Safari + VoiceOver
• iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information

We are tracking known screen reader bugs in
here. If you find a screen reader bug,
please check it against this list.

Keyboard Navigation

This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.

Magnification

This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test magnfication and make sure it is working as intended and well with the use cases of the
simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen
reader so there is no need to test this case.

---

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.

---

[zepumph]

@kathy-phet has added this to active tests, and asked for the dev versions to be created. Done!

[KatieWoe]

Calling QA here

[zepumph]

Excellent! Thanks. I'll try to make an RC tomorrow.