Prototype test: Greenhouse Effect 1.0.0-rc.1

[jbphet]

@kathy-phet and @arouinfar -Greenhouse Effect 1.0.0-rc.1 is ready for prototype testing. This simulation will be
put on the website as a prototype and will likely have more bugs than a publication-ready simulation. Document issues in
https://github.com/phetsims/greenhouse-effect/issues and link to this issue. Issues should focus on base usability and
pedagogy.

This release does include phet-io, so the testing should also include basic aspects of this brand.

Assigning to @kathy-phet and @KatieWoe for prioritization.

General RC Test

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".

Focus and Special Instructions

[Provide further instructions here. Any aspects or requests not included elsewhere can be included here]

Known Issues

• IR waves returning to earth aren't connected to original wave
• IR waves become very thin and barely visible in Studio

These issues should have the "status:ready-for-qa" label if they are fixed. Check these issues off and close them if they are fixed.
Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. Most of these issues will not be fixed
at this point, just be aware of them as you test.

Link(s)

• Simulation
• PhET-iO
• Test Matrix

---

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

[jessegreenberg]

Thanks QA team! Moving on to next RC.