RC test: Graphing Slope-Intercept 1.1.0-rc.1

[pixelzoom]

@KatieWoe , @ariel-phet , @amanda-phet graphing-slope-intercept/1.1.0-rc.1 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-slope-intercept/issues and link to this issue.

NOTE: For efficiency, this should be tested at the same time as Graphing Lined 1.3.0-rc1, see #277.

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

• disable showAnswers in production versions

Additionally, these Graphing Lines issues (being tested in #277) also apply to Graphing Slope-Intercept:

• prioritize active line when color-coding point tool
• use icons for "Hide lines" and "Hide grid"
• do not disable UI components when graph contents are hidden
• use standard font for math symbols
• Eliminate GamePhaseProperty

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

---

[KatieWoe]

Memory Test Results:
Start: 30.8
1 min: 42.9
2 min: 42.7
3 min: 44.0
4 min: 44.5
5 min: 44.3
6 min 44.4
7 min: 45.4
8 min: 46.2
9 min: 46.0
10 min: 47.3

[KatieWoe]

QA is done

[pixelzoom]

Thanks QA team! We'll need another RC, and I'll keep this issue open until I've created the corresponding issue.

[pixelzoom]

1.1.0-rc.2 testing started in #284.