RC test: Graphing Lines 1.3.0-rc.4

[pixelzoom]

@KatieWoe , @ariel-phet , @amanda-phet graphing-lines/1.3.0-rc.4 is ready for RC testing. This is a brand=phet release only (no PhET-iO, no a11y).

Document issues in https://github.com/phetsims/graphing-lines/issues and link to this issue.

NOTE: This should be tested at the same time as Graphing Slope-Intercept 1.1.0-rc.4 (#291).

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.

Issues to Verify

Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed. These issues are all platform independent; if they work on one platform, they will work on all platforms. So a full test matrix is unnecessary for this RC. Spot checking on a couple of platforms is sufficient.

This issue is specific to Graphing Lines:

• Impossible challenge

These issues must be tested for both Graphing Lines and Graphing Slope-Intercept (#291):

• Slope writing is inconsistent size
• Short max widths for game answers
• Very slight pointer area overlap with number pickers

Link(s)

• Simulation
• iFrame
• XHTML
• Test Matrix
• 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 also marking as top priority since this is a spot check and hopefully should polish this sim off

[KatieWoe]

Since this is a spot check, these are the platforms I would propose checking. @pixelzoom let me know if you want any changes.

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

---

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

---

• iOS 12
• iOS 10
• chrome OS

---

• Win 7 IE
• Mac 10.12 safari

[KatieWoe]

QA is done

[pixelzoom]

Thus concludes RC testing for the 1.3.0 release, we're ready to publish.

Thanks @KatieWoe and QA team. While I'm somewhat mortified that this took 4 RCs, you found some good stuff, much of which has been lurking in the code since the Java version.