RC test: Natural Selection 1.3.0-rc.2

[pixelzoom]

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

The publication deadline is 4/30/21, which is 2 days from now.

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. In addition to whatever you typically do for a spot-check, it is sufficient to test only "Issues to Verify".

Issues to Verify

• Population panel shows incorrect checkboxes with ?stringTest natural-selection#269
• Update credits for 1.3 release natural-selection#270

See the last comment in each issue for instructions on how to verify. It is sufficent to verify these issues on 1 platform of your choosing.

These issues are labeled "status:ready-for-qa". Check these issues off and close them if they are fixed.

Link(s)

• Simulation
• iFrame
• XHTML

---

PhET-iO RC Test

What to Test

This is a spot-check test. In addition to whatever you typically do for a spot-check, it is sufficient to test only "Issues to Verify".

Issues to Verify

• Improve public-facing documentation of mutation and population query parameters natural-selection#259 @amanda-phet
• Update screenshot in PhET-iO Guide. natural-selection#273 @amanda-phet
• Diff wrapper is broken. natural-selection#271
• Studio tree highlighting clears when toggling Featured/All elements natural-selection#272

See the last comment in each issue for instructions on how to verify. It is sufficent to verify these issues on 1 platform of your choosing.

These issues are labeled "status:ready-for-qa". Check these issues off and close them if they are fixed.

Note that two of the above issues should be verified by @amanda-phet (as labeled, and assigned). These issues deal with changes to the PhET-iO Guide, and it will quicker for her to verify.

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]

• Win 10 Chrome (Time = 1)
• Win 10 Firefox (Time = )
• MacOS Safari (Time = 0.5 hr)
• MacOS Chrome (Time = 0.5 hr)
• ChromeOS (Time = )
• iPadOS (Time = )

[KatieWoe]

Spot-check is done

[pixelzoom]

Thanks for the quick turnaround @KatieWoe and QA team.

Another RC spot-check coming up, to test the Diff Wrapper.

Closing.