Dev Test: Greenhouse Effect 1.1.0-dev.9

[jbphet]

Dev Test

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

Simulation links

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

Test Matrix

Please include all (non-screen reader) feature testing in these records if applicable.

• Latest macOS, Safari (Time = 2hrs)
• Windows 10, Chrome (Time = 3hrs)
• Windows 10, Firefox (Time = 2hrs)
• Latest iOS, Safari (Time = 1)
• Windows 11, Chrome (Time = 2.5)

Light testing, or optionally skip if time crunch:

• Latest macOS, Chrome (Time = )
• Latest Chrome OS, Chrome (Time = )

If screen readers are being tested:

• Win 10/11 Chrome + Jaws (Time = 3.5)
• Win 10/11 Firefox + NVDA (Time = 2hrs)
• MacOS Safari + VO (Time = 3.5hrs )
• iPadOS Mobile VO (Time = 2.25hrs)

Features included

• Alternative Input
• UI Sound
• Sonification
• Description

Focus and Special Instructions

This sim is about to have some interview testing done on the description present in the first screen, so this QA testing
should focus on making sure that it is ready for these interviews. Only the first screen should be tested, and the link
above uses the screens query parameter to prevent the other screens from being shown, but note that they are present
in this version and will appear if launched without the query parameter. No testing should be done on these screens.

Keyboard navigation should also be a part of this testing.

The sim was released a while back as a prototype with only the first screen, so some testing should also be done on the
basic functionality to make sure that no regressions were introduced.

Sound has been added, and should also be tested as part of this.

No PhET-iO testing needs to be performed for this dev release.

Issues to Verify

There are no specific GitHub issues that need to be verified during this testing.

---

For QA...

General features

What to Test

• Click every single button.
• 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.
• Try to include browser version numbers
• If there is a console available, check for errors and include them in the Problem Description.
• Run through the string tests on at least one platform, especially if it is about to go to rc.
• Check the Game Up harness on one platform.

---

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

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

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
this Google Document. 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]

Memory test:

[KatieWoe]

QA is done

[jbphet]

Thanks QA team. I'll follow up in the individually logged issues. Closing this one.