RC Spot-Check Test: Graphing Slope-Intercept 1.2.0-rc.2

[pixelzoom]

RC Spot-Check Test

Mentions: @amanda-phet

Simulation links

• github repository for issues
• phet top-level directory
• sim: all_phet.html

Test Matrices

General Test:

• Tester = NS , Platform = mac + safari/chrome, Time = .25
• Tester = KW, Platform = Win 11 Chrome, Time = .25

Additional Features Test:

• Tester = , Platform = , Time =
• Tester = , Platform = , Time =

Features included

• Region and Culture (R&C)
• Dynamic Locale
• UI Sound
• PhET-iO
• Alternative Input
• Sonification
• Description
• Voicing

Focus and Special Instructions

Plan to do this test at the same time as #1074, since Graphing Slope-Intercept is derived from Graphing Lines.

Issues to Verify

These issues have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.

• Text repositioning delayed when switching locals graphing-lines#152
• Memory leak graphing-lines#153
• Update credits for 1.4 release graphing-lines#155
• Drag Listeners aren't interrupted graphing-lines#156
• Text shifts in top banner of game level with ?stringTest=dynamic graphing-lines#158
• Start Over button can overlap text with ?stringTest=dynamic graphing-lines#159

---

For QA...

General features

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 some query parameters. (See QA Book for a
  list of query parameters.)
• When making an issue, check to see if it was in a previously published version.
• Try to include version numbers for browsers.
• If there is a console available, check for errors and include them in the Problem Description.
• As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there
  is a problem.
• As the RC ends, notify the developer of any new QA credits that need to be added.

---

PhET-iO features

What to Test

• Make sure that public files do not have password protection. Use a private browser for this.
• Make sure that private files do have password protection. Use a private browser for this.
• Make sure standalone sim is working properly.
• Make sure the wrapper index is working properly.
• Make sure each wrapper is working properly.
• Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
• For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
  sure the simulation loads without crashing or throwing errors.
• Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:

  /wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER
  

  Further instructions in QA Book
• Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other
  random platform.
• Conduct a memory test on the stand alone sim wrapper (rc.1).
• Test one platform combination with ?phetioDebug=true on the Studio and State wrapper.
• If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
• Test that the sim works offline:
  • Click the link to the phet-io zip file (at top of issue) to download the zip file.
  • Unzip it to a spot locally.
  • Open index.html by double clicking it on your desktop or in a Finder-view.
  • It should look like the standalone version of the sim in PhET-iO brand.

---

Accessibility features

What to Test

• Specific instructions can be found above.

• Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
  a list of features that may be supported in this test:

  • Alternative Input
  • Interactive Description
  • Sound and Sonification
  • Pan and Zoom
  • Mobile Description
  • Voicing

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

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

Screen Readers

This sim may support 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
here. 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.

Magnification

This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test magnfication and make sure it is working as intended and well with the use cases of the
simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen
reader so there is no need to test this case.

---

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]

QA is done

[pixelzoom]

Thanks for the quick turnaround! We're ready to publish 1.2.0. 🎉