RC test: Natural Selection 1.1.0-rc.1

[pixelzoom]

@amanda-phet @ariel-phet, natural-selection/1.1.0-rc.1 is ready for RC testing. (@KatieWoe as with #539, you can ignore this issue. It will be spot-checked by @amanda-phet and @ariel-phet.)

The deadline to complete testing is noon on Tuesday, 9/1/2020.

Document issues in https://github.com/phetsims/natural-selection/issues and link to this issue.

Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

• Click every single button.
• Test all possible forms of input.
  • Test all mouse/trackpad inputs.
  • Test all touchscreen inputs.
• 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.
• Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
• Download HTML on Chrome and iOS.
• Make sure the iFrame version of the simulation is working as intended on all platforms.
• Make sure the XHTML version of the simulation is working as intended on all platforms.
• Complete the test matrix.
• Don't forget to make sure the sim works with Legends of Learning.
• Test the Game Up harness on at least one platform.
• Check this LoL spreadsheet and notify AR or AM if it not there.
• If this is rc.1 please do a memory test.
• When making an issue, check to see if it was in a previously published version
• Try to include version numbers for browsers
• If there is a console available, check for errors and include them in the Problem Description.
• As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem.

Focus and Special Instructions

Since #539 revealed no serious issues, this is a spot check. Test on a couple of devices, and verify the issues in "Issues to Verify". Be sure to test everything in the "Links" section below, including the LoL test harness.

Issues to Verify

• Appearance of "Zoom out to see data." is inconsistent
• Population graph layout issue with very long strings

These issues should have the "status:ready-for-qa" label. 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. If the label is
"status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

Link(s)

• Simulation
• iFrame
• XHTML
• Test Matrix
• Legends of Learning Harness

---

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.

---

[ariel-phet]

I have completed my testing. Everything look good on Win browsers, and iPad Air 2,

• I also double checked that strings Tests were passed for short strings after the very long string test issue was fixed.
• verified that iFrame looked good

@pixelzoom my testing is done here. I think once @amanda-phet gives the green light, we can proceed with a spot check. We should ask Katie to check the LoL test harness (I am not sure how to do that) for the spot check.

[amanda-phet]

I tested iPad air on Safari. I thought it was all looking good!

Was @oliver-phet going to test Mac?

[pixelzoom]

@oliver-phet and @phet-steele were not going to be involved in the RC testing.

[pixelzoom]

@amanda-phet do you want to have a look on Mac before I proceed with the next RC?

[amanda-phet]

Yes I probably should.. Unfortunately I might not be able to until later today. But I will have it done by 2pm at the latest.

[pixelzoom]

Let's move ahead with the next RC and test that one on Mac. I'm confident that macOS is not a problem.

[amanda-phet]

Sounds good. I also did a quick check on both Chrome. I've used it in Safari a ton and I know it's fine.

[pixelzoom]

Then onward to the next RC, in #542.

Closing.