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

[mbarlow12]

After a minor big was introduced in RC 7, I released the updated version. Below is a copy from the previous issue.

@KatieWoe, @arouinfar, @jessegreenberg, @ariel-phet coulombs-law/1.0.0-rc.8 is ready for a final spot RC check. Document issues in https://github.com/phetsims/coulombs-law/issues and link to this issue.

There are a few issues discovered from the last RC that won't be addressed prior to this publication. They are noted below.

Assigning @ariel-phet for prioritization.

General RC Test

What to Test

• Click every single button.
• 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.)
• Complete the test matrix.
• Check this LoL spreadsheet and notify AR if it not there.

Issues to Verify

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.

• Text goes off screen
• Dilate touch areas on charge NumberControls
• Forces are not equal and opposite

iOS crashing is apparently no longer an issue, but we should still check to ensure it doesn't arise again.

• Crash on iOS 10

The following issues won't be addressed prior to publication.

• Legends of Learning page freeze
• Moving one charge can move the other charge
  • inconsistently appears and is possibly a FF-specific issue
• Jumpy distortion on Firefox while resizing window
  • appears to be another FF bug
• Keyboard Nav Issues
  • issues witnessed are actually desired/standard behavior

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

Link(s)

• a11y View
• Simulation
• Test Matrix

Keyboard Navigation

This sim supports keyboard navigation. Please make sure it works as intended.

---

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.

---

[KatieWoe]

• Win 10 chrome Full
• Win 10 firefox
• Win 10 edge Full

---

• Mac 10.14 chrome
• Mac 10.14 firefox Full
• Mac 10.14 safari Full

---

• iOS 12 Full
• iOS 10

---

• Chrome OS

---

• Win 7 IE Full
• Win 7 chrome
• Mac 10.11 safari
• Mac 10.11 firefox

[KatieWoe]

Keyboard nav seems to behave a bit oddly if you start in after manipulating one of the charge sliders. I'm in firefox, but chrome was being a bit odd too. I don't think its broken, but you might want to take a look for yourself. It takes two key presses to start in firefox, and it starts in an unexpected location.
But it doesn't do this if you were manipulating anything but those sliders. Chrome does something similar, but it starts at the beginning after manipulating the sliders. Same with edge. Not sure if this is issue worthy. Let me know.

[KatieWoe]

@mbarlow12 QA is done. @jessegreenberg and @mbarlow12 should decide on severity of #243 (comment)

[mbarlow12]

@KatieWoe that's definitely not working properly. There seems to be some odd behavior with NumberControls that the a11y team will need to sort through. Thanks for catching!

[KatieWoe]

I'll put it in an issue.