Dev test: Coulomb's Law 1.0.0-dev.19

[mbarlow12]

@arouinfar , @emily-phet , @jessegreenberg coulombs-law/1.0.0-dev.19 is ready for dev testing. Document issues in https://github.com/phetsims/coulombs-law/issues and link to this 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.

General Dev Test Platforms

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

Issues to Verify

• Missing string found in CT (should be fixed now)

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)

• Coulomb's Law

---

Accessibility (a11y) Dev Test

What to Test

• Specific instructions can be found below.
• Make sure the a11y feature doesn't negatively affect the sim in any way.

Focus and Special Instructions

See the issues below, but please pay special attention to keyboard navigation within Firefox.

Issues to Verify

• Firefox lags with ruler keyboard dragging

Please note that this hasn't been specifically fixed as we couldn't really ascertain the cause. We opted to push its full fix to 1.1, but it would be useful to know if this is still persisting and any more details that we may not have gathered in the first round.

Link(s)

• a11y View
• Coulolmb's Law (a11y)

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.

---

[arouinfar]

It's super exciting to see CL moving into QA testing!

@mbarlow12 it was my understanding that CL would be published without any a11y features. While it's true that keyboard navigation is functional with ?accessibility, it's missing the keyboard dialog (phetsims/coulombs-law#58 (comment)) and there's a also a known keyboard nav issue with the ruler (phetsims/coulombs-law#41). Both of these issues were deferred until version 1.1+. Perhaps this issue should be amended to remove a11y testing.

[arouinfar]

Well, it looks like I commented a bit soon, my bad. I didn't see the separate a11y links. Definitely seems reasonable for QA to test keyboard nav, so long as @KatieWoe and team are aware of the scope.

[ariel-phet]

@KatieWoe this task is similar priority to #199 since both are new sims, and this would be an exiting one to get published.

[mbarlow12]

@arouinfar Thanks for the notice. I'd missed the keyboard help dialog. I'll add that today, update the dev release and the issue here.

[arouinfar]

@mbarlow12 since keyboard nav is deferred until 1.1, I'm not sure that the dialog is necessary, but I'll leave it up to you.

[emily-phet]

I may be mis-remembering, but I believe a11y features were deferred because there was some urgency to get additional sims out for the start (or at least, early part of) the Fall start to school. Since that's not the case now, I don't see any reason to defer deploying with keyboard nav, if all it takes is adding in the already designed dialog, and QA testing keyboard nav. If significant issues come up in QA testing, we can triage from there and decide to defer at that point if necessary.

Does this seem reasonable @ariel-phet ?

[arouinfar]

That all sounds reasonable to me @emily-phet, so long as @mbarlow12 has the bandwidth for it.

[KatieWoe]

QA is done

[mbarlow12]

@KatieWoe after the updates from @jessegreenberg in phetsims/john-travoltage#317, is the full screen IE issue resolved for CL and GFL(:B)?

If so, then with the ruler dragging deferred to 1.1, I'd say we can move on to the next stage.

[KatieWoe]

@mbarlow12 phetsims/john-travoltage#317 (comment)
Yes it should be resolved for both sims.

[mbarlow12]

@ariel-phet do I have the go ahead to move into RC testing?

[ariel-phet]

@mbarlow12 sort of....I don't see the keyboard dialog?

Could you publish a version that includes the keyboard dialog...I don't see it when I run
https://phet-dev.colorado.edu/html/coulombs-law/1.0.0-dev.19/phet/coulombs-law_all_phet.html?accessibility

Please publish a dev version that includes that, and have @arouinfar do a quick spot check of the dialog, and if all looks good feel free to move onto RC. Make sure the RC also includes a check of the projector mode.

[mbarlow12]

@arouinfar @ariel-phet here's a new dev version with the keyboard help dialog.

https://phet-dev.colorado.edu/html/coulombs-law/1.0.0-dev.20/phet/coulombs-law_en_phet.html

Let me know what tweaks need to be made before heading to RC.

[arouinfar]

Looks good @mbarlow12!

[phet-steele]

RC in #210.