RC test: Natural Selection 1.2.0-rc.1

[pixelzoom]

@amanda-phet, @kathy-phet, @ariel-phet, @oliver-phet, @KatieWoe natural-selection/1.2.0-rc.1 is ready for RC testing.

This RC is for the deliverable described in phetsims/natural-selection#208. Deadlines are:

• testing of this RC should be completed by 9/23/2020
• delivery of an RC version to the client by 10/1/2020

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

This is an RC Lite test. Test platforms are the same as a dev test:

• Latest macOS, Chrome and Safari
• Latest iOS, Safari
• Windows 10, all browsers (IE dropped)
• Latest Chrome OS, Chrome

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

This RC is for PhET-iO brand only. While PhET-iO should be the major focus, please do fully test the sim.

See the Client Guide for client-specific requirements that should be tested.

No links to the PhET brand are included here because we will not be testing it for this RC.

PhET-iO RC Test

What to Test

• Make sure that public files do not have password protection. Use a private browser for this.
• Make sure that private files do have password protection. Use a private browser for this.
• Make sure standalone sim is working properly.
• Make sure the wrapper index is working properly.
• Make sure each wrapper is working properly.
• Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
• For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
  sure the simulation loads without crashing or throwing errors.
• N/A For an update or maintenance release please check the backwards compatibility of the playback wrapper.
• Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:

  /wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER
  

  Further instructions in QA Book
• Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other random platform.
• Conduct a memory test on the stand alone sim wrapper (rc.1).
• Test one platform combination with ?phetioDebug on the Studio and State wrapper.

Focus and Special Instructions

[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested,
list them here. Any behaviors you want QA to pay special attention to should be listed here.]

Issues to Verify

• memory test for brand=phet-io (1.2 branch) - since this is the first RC on a new branch (1.2), please confirm the results shown in this issue

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)

• Wrapper Index
• 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]

Playback wrapper seems to be exceedingly slow on Mac 10.15 Chrome for both loading log and starting playback. Having trouble even getting it to start. @zepumph please advise. In fact it seems to have timed out: Failed to load resource: net::ERR_CONNECTION_RESET

[KatieWoe]

Noting a fair amount of slowdown between generations on ChromeOS when looking at a data stream (such as colorized).

[pixelzoom]

@KatieWoe I don't know whether slowdown in the colorized data stream wrapper is an issue. I think it would be expected with NS, since it's doing a massive amount of writing to the console, and I don't know how it could be addressed. If you think it's significant, please create an issue.

[KatieWoe]

I don't know if it's significant. It is a massive amount of slow down, but I don't know how important performance is in that wrapper.

[KatieWoe]

QA is done.

[pixelzoom]

Thanks @KatieWoe.

Your comments in #551 (comment) and #551 (comment) have been promoted to their own issues.

[pixelzoom]

@KatieWoe The test matrix shows errors for #376 and #377. There are no such issues in the natural-selection repo. I eventually found them in phet-io-wrappers. When an issue is in another repo, could you please note in the test matrix as (e.g.) phet-io-wrappers#376 ?

[pixelzoom]

Next RC test created in #557. Closing.