Dev Test: Greenhouse Effect 1.2.0-dev.2

[jbphet]

Dev Test

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

Simulation links

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

Test Matrix

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

• Latest macOS, Safari (Time = 2)
• Windows 10, Chrome (Time = .75)
• Windows 10/11, Firefox (Time = 3.0)
• Latest iOS, Safari (Time = 2)
• Windows 11, Chrome (Time =2 )

Light testing, or optionally skip if time crunch:

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

If PhET-iO is being tested:

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

Features included

• PhET-iO
• Alternative Input
• UI Sound
• Sonification

Focus and Special Instructions

The primary purpose of the next release of this sim is to add full support for phet-io, and this dev test is the first
round of verification for that functionality. The focus should be on phet-io support while simultaneously regression
testing the basic functionality of the sim.

---

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.

---

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.

---

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

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]

Noting that the sound on iPad is fairly staticky. This is the same in published.

[KatieWoe]

Not necessarily a bug, but I noticed that, since the default temp units are now in the preferences menu, the teacher tips should be updated to reflect that when this is published.

[KatieWoe]

QA is done

[jbphet]

Thanks QA team! I'll close this issue and will address the individual issues listed above.