Prototype test: Natural Selection 1.0.0-rc.1

[pixelzoom]

@amanda-phet, @ariel-phet, @kathy-phet, @KatieWoe, natural-selection/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/natural-selection/issues and link to this issue. Issues should focus on base usability and pedagogy.

Assigning to @ariel-phet 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

There are many sim-specific query parameters in NaturalSelectionQueryParameters.js. The only one that you need to consider for prototype testing is secondsPerGeneration (default 10), which determines how long it takes to complete 1 cycle of the generation clock. Decrease this value to make the clock run faster.

Link(s)

• Simulation
• 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.

---

[ariel-phet]

@KatieWoe assigning this one directly to @phet-steele as he expressed interest in performing this test as a way to "get back to the swing of things"

@phet-steele marking as medium priority as this test does not need to be extensive, but teachers will definitely be excited for the prototype version so sooner is better from that regard

[ariel-phet]

In terms of important testing this prototype is basically done (thanks @phet-steele!)

I will do some cursory testing on an iPad and ask @amanda-phet and @oliver-phet to take a quick look on Mac

[pixelzoom]

The 4 issues identified by @phet-steele have been addressed, awaiting review and verification in the next RC.

Assign this issue to me when @ariel-phet and @oliver-phet have complete their "quick looks" and I'll proceed with the next RC. The next RC can likely be a "spot check" to verify the issues that @phet-steele identified.

[pixelzoom]

We'll also need to verify the model changes the @amanda-phet requested in the next RC -- phetsims/natural-selection#152, phetsims/natural-selection#153.

[amanda-phet]

I believe the testing matrix is complete now.

[pixelzoom]

In retrospect we should have done a dev test first. There have been a lot of changed required for this RC. And it has become increasingly difficult (and time-consuming) to patch changes into the 1.0 branch, to the point where forward progress on master has ground to a halt. After consulting with @ariel-phet, I'm going to give up on trying to patch the 1.0 branch, and only make changes in master. The next RC will either be in a new 1.1 branch, or I will merge all changes from master into 1.0. And before that RC, we'll do a quick test on a dev version.

[pixelzoom]

There's a new plan for the prototype, see phetsims/natural-selection#116 (comment).

Closing this issue.