RC test: Coulomb's Law 1.0.0-rc.4

[mbarlow12]

@KatieWoe, @arouinfar, @jessegreenberg, coulombs-law/1.0.0-rc.4 is ready for RC testing. Document issues in https://github.com/phetsims/coulombs-law/issues and link to this issue.

Assigning @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.

Issues to Verify

• Keyboard nav focus gets lost in iFrame #74
• Navigation bar icons look bad in Firefox #75
• Keyboard Navigation Dialog #58

NOTE: keyboard dialog issue has been closed, but I thought it'd be useful to confirm.

Link(s)

• Simulation
• iFrame
• XHTML
• Test Matrix
• Legends of Learning Harness

---

Accessibility (a11y) RC Test

What to Test

• Specific instructions can be found below.
• Make sure the a11y feature doesn't negatively affect the sim in any way.
• 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).

Link(s)

• a11y View
• Simulation
• Test Matrix

Keyboard Navigation

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

---

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]

@KatieWoe top testing priority for the moment

Mentioning @rea-laura @phet-steele @JRomero0613 @lmulhall-phet since Katie is at a conference

[JRomero0613]

The test matrix link provided does not direct to the test matrix and instead directs to a blank github page. Could a new link be provided so testing progress can be updated?

[ghost]

I’ll make a matrix in a second! Sorry about that, @JRomero0613.

[ghost]

Link should be working now.

[KatieWoe]

QA is done.

[KatieWoe]

Sorry, @mbarlow12, noticed one last thing. Apparently the pointer areas for the reset button for touch should be larger. https://github.com/phetsims/friction/issues/65

[mbarlow12]

Only issues remaining after latest commits are:
phetsims/scenery#890
and
phetsims/scenery#883

[mbarlow12]

Closing. New RC issue at #221