RC test for build-a-fraction 1.0.0-rc.2

[jonathanolson]

@amanda-phet, @ariel-phet, @kathy-phet, build-a-fraction/1.0.0-rc.2 is ready for RC testing. There is a hard deadline of January 31st (it's a Google sim). Document issues in https://github.com/phetsims/fractions-common/issues and link to this issue.

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 if it not there.
• If this is rc.1 please do a memory test. JO NOTE: This sim can use a decent amount of memory. I've been resetting all screens first and it is quite stable, but if every level of each game has been interacted with (and fuzzing pulls out hundreds of pieces in the labs/etc.) then it can use a lot of memory.

Issues to Verify

• Up/down spinner fix for ranges
• Dragging number groups
• Edge switched to SVG instead of Canvas - test Edge

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)

• Simulation
• iFrame
• XHTML
• Legends of Learning Harness

---

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 considering nothing too major was found in RC.1 and code fixes were minor, this test should mainly be a spotcheck to verify issues were fixed. A bit of extra testing should be done on Edge since the renderer was switch from canvas to SVG

[KatieWoe]

Per @jonathanolson on slack. @ariel-phet is this alright?

• Win 10 edge
• Mac OS 10.14 chrome
• Mac OS 10.14 firefox
• iOS 12
• iOS 10

[KatieWoe]

QA is done

[jonathanolson]

Thanks!