Dev-Lite Test: Greenhouse Effect 1.1.0-dev.12

[jbphet]

Dev-Lite Test

This is a dev lite test of the first screen only for the Greenhouse Effect sim. This test is being done to make sure
that the sim is ready for a set of interviews that will be focused on testing interactive description. This is the
third dev test for this, and several issues have been addressed based on the first two dev tests.

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

Simulation links

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

Test Matrix

• Tester 1 (Tester = E2, Platform = Win10 Firefox, Time = 2 {max 2 hours}
• Tester 2 (Tester = NS, Platform = mac + safari/VO, iPad +VO (briefly), Time =2hrs {max 2 hours}

Features included

• Alternative Input
• UI Sound
• Sonification
• Description

Focus and Special Instructions

The focus for this testing should be almost entirely on description, but please keep an eye out for any bugs that would
cause problems in interviews.

Issues to Verify

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

• Shorten time period descriptions greenhouse-effect#200
• When concentration = none, IR redirected should be "No" not "Less" greenhouse-effect#201
• Further updates to Explore Mode RadioButtonGroup Responsive Descriptions greenhouse-effect#199
• Minor grammatical changes greenhouse-effect#202

---

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
  • Mobile Description

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

---

[jbphet]

Over Slack, @arouinfar said:

Campus move-in is next week which makes it difficult to do on-campus interviews, so I am thinking about scheduling the interview for Friday [8/12/2022] instead. I know that only gives us a day for QA testing and assumes there aren’t any major issues to fix. Worst case we can fall back to the previous dev version for this interview.

With this goal in mind, the QA team should probably view this as a pretty quick sanity test. Please be in contact with @arouinfar for any more information, and assign the issue to her once completed.

[jessegreenberg]

@Nancy-Salpepi verified that a new change added after dev.11 has fixed phetsims/greenhouse-effect#192. I built a new dev version with this fix so that further testing can include it. Links for this issue have been updated to dev.12 to include the change.

[Nancy-Salpepi]

Passing the baton over to you @arouinfar!

[arouinfar]

Thanks for the quick turnaround @Nancy-Salpepi! I ended up using dev.13 in the interview, and it went well.