Prototype test: Greenhouse Effect 1.1.0-rc.3

[jbphet]

Prototype Test

Mentions: @arouinfar, @kathy-phet, @KatieWoe

Simulation links

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

Test Matricies

• Tester = NS , Platform = mac + safari , Time = .75
• Tester = KW, Platform = Win 11 Chrome, Time = .5

Features included

• Alternative Input
• UI Sound
• Sonification

Focus and Special Instructions

Three issues were addressed as a result of the previous round of testing, and two were pretty minor, so this round of
testing can be relatively light. Verifying the issues should be the focus, and there should be additional verification
of the energy balance indicator and the flux meter, since there were some non-trivial changes made to them to improve
their performance.

Issues to Verify

• Overlapping long strings greenhouse-effect#246
• Update QA credits for the 1.1 prototype release greenhouse-effect#260
• Jerky animation on low-performance device greenhouse-effect#265

---

For QA...

General features

What to Test

• Play with the simulation normally.
• Make sure you can't lose anything.
• Complete the test matrix.
• Try to include version numbers for browsers
• If there is a console available, check for errors and include them in the Problem Description.
• Focus on pedagogy issues and bugs that break the sim.
• If you find bugs beyond pedagogy/breaking, still document these bugs as github issues.
• If a11y aspects are present, test them, but with an eye for "normal use".

---

Accessibility features

What to Test

If a11y aspects are present, test them, but with an eye for "normal use".

• 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

[jbphet]

Thanks QA team! I'll check over the issues and take the next steps. Closing.