RC test: Natural Selection 1.3.0-rc.3

[pixelzoom]

@KatieWoe, @kathy-phet, @amanda-phet natural-selection/1.3.0-rc.3 is ready for RC testing.

The publication deadline is 4/30/21.

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

This is a spot-check test for phet and phet-io brands. See "Issues to Verify" for testing instructions.

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

General RC Test

What to Test

This is a spot-check test. There are no issues to verify that are specific to brand=phet, and there have been no sim-specific changes. So just test the links, give the sim a quick look, and call it good.

Link(s)

• Simulation
• iFrame
• XHTML

---

PhET-iO RC Test

What to Test

This is a spot-check test. It is sufficient to test only "Issues to Verify".

Issues to Verify

• Diff wrapper is broken. natural-selection#271 (Diff wrapper is broken)

See the last comment in the issue for instructions on how to verify. It is sufficent to verify on 1 platform of your choosing. If verified, check the issue off and close it.

Link(s)

• Wrapper Index

---

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]

Spot check done

[pixelzoom]

Thanks for the quick turnaround @KatieWoe and QA team. This concludes RC testing for 1.3. Onward to publication!