Prototype test (RC-lite): Greenhouse Effect 1.1.0-rc.2

[jbphet]

Prototype Test (RC-lite)

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

Simulation links

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

Test Matricies

• General Test Matrix

Features included

• Alternative Input
• UI Sound
• Sonification

Focus and Special Instructions

Quite a few issues were addressed as a result of the first round of testing, but none of them required any major
changes to the code base, so this testing can be a "lite" round of testing that focuses on verifying that the listed issues have
been addressed and does some basic regression testing.

Issues to Verify

• Add keyboard help information for interaction with the flux meter greenhouse-effect#180
• Sound from Waves screen heard on other screens greenhouse-effect#238
• Interactive highlight placement is odd greenhouse-effect#239
• In arrow cut off in Energy Graph greenhouse-effect#240
• Pausing before starting sunlight looks odd greenhouse-effect#241
• Temperature checkbox can get covered by Energy Balance panel greenhouse-effect#242
• Keyboard pause or play action different for Mac greenhouse-effect#243
• Recommend making touch area larger for flux meter greenhouse-effect#245
• Overlapping long strings greenhouse-effect#246
• Focus highlight outside dev bounds greenhouse-effect#247
• Flux Meter overlaps Energy Balance / Flux Meter checkbox panel greenhouse-effect#248
• Flux Meter stroke extends past dark overlay before sunlight starts greenhouse-effect#250
• Surface temperature layer doesn't exactly match artwork below greenhouse-effect#251
• Hard to see photons greenhouse-effect#252
• Screenshots missing photons greenhouse-effect#255
• Inconsistent outline around temperature values in combobox greenhouse-effect#256
• Timing Controls section in dialog doesn't change in string tests greenhouse-effect#257
• Update QA credits for the 1.1 prototype release greenhouse-effect#260
• This comment from the previous test that I (@jbphet) didn't notice until I was creating this issue concerns me. Please test again, and if the performance of this sim is noticeably less smooth than that of of other animation-based PhET sims, please log an issue.

---

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

[KatieWoe]

RC 3 is out. Closing