RC Test: gravity-force-lab-basics:1.0.0-rc.2

[zepumph]

@terracoda, @emily-phet, @jessegreenberg, gravity-force-lab-basics:1.0.0-rc.2 is ready for RC testing. This is the second RC test for this sim (see #429). This is being published for the first time, and includes sound as well as Interactive Descriptions. Document issues in https://github.com/phetsims/gravity-force-lab-basics/issues and link to this issue. There are many changes from the previous version, and a few were difficult to copy from master, so I would recommend testing a bit more thoroughly than just a a spot check here. Especially as it pertains to the descriptions.

Assigning to @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 or AM if it not there.
• If this is rc.1 please do a memory test.
• When making an issue, check to see if it was in a previously published version
• If there is a console available, check for errors and include them in the Problem Description.

Issues to Verify

Instead of just issues, these are links directly to the comment which should have the instructions about what to verify:

• Should get "closest" alert when closest with a constant radius
• Need to double check that Size of Arrows and Effort of Robots (cancel out)
• Investigate best min and max values for mass sliders
• iPadOS 13 Checkboxes won't select/deselect with VO but the general issue is here I don't think there is any difference between the two, but feel free to close both if helpful when checking.

This sim was also not included in some of the batch maintenance releases that recently went out, so please make sure these are fixed in this rc as well:

• Depressed buttons on iOS 13 look wrong
• iOS 13 Full Screen enabled

These issues should have the "status:ready-for-qa" 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 and link back to this issue. If the label is "status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

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

Screen Readers

This sim supports 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 this Google Document. 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.

Final Requests

• If this sim is in this list, make an issue in website to ask if PhET research page links need updating. Please assign to @terracoda and @emily-phet.

---

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.

---

[ghost]

Making top since we don't have anything else in the repo right now. (Except for issues that are languishing.)

[KatieWoe]

@jonathanolson mentioned it, but #432 (comment) needs to be implemented here.

[ariel-phet]

bumping down to high priority, since #432 is for fixes to broken sims that are "live" in the world.

[KatieWoe]

#432 (comment) was not applied. That means that phetsims/phet-core#64 failed I believe

[KatieWoe]

QA is done

[zepumph]

Thanks! We will proceed with a spot check rc over in phetsims/gravity-force-lab-basics#184 (comment).