Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev test: Natural Selection 1.3.0-dev.1 #573

Closed
12 tasks
pixelzoom opened this issue Nov 2, 2020 · 4 comments
Closed
12 tasks

Dev test: Natural Selection 1.3.0-dev.1 #573

pixelzoom opened this issue Nov 2, 2020 · 4 comments
Labels
QA:dev-test Dev test before an RC status:on-hold

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Nov 2, 2020

NOTE: Creation of this dev version is delayed until this issue is in the QA Active Tests list.

@amanda-phet, @ariel-phet, @kathy-phet, @KatieWoe, simulation-name/1.3.0-dev.1 is ready for dev testing. The 1.3 release will be for both phet and phet-io brands, and will involve a full QA cycle. Release plan is documented in phetsims/natural-selection#251.

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

Assigning to @ariel-phet for prioritization.

General Dev Test

What to Test

  • Click every single button.
  • 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.
  • Try to include browser version numbers
  • If there is a console available, check for errors and include them in the Problem Description.
  • Run through the string tests on at least one platform, especially if it is about to go to rc.
  • Check the Game Up harness on one platform.

General Dev Test Platforms

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

Issues to Verify

These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for
QA then close the issue if fixed. If ready for review then leave open and assign back to the developer.

Link(s)


PhET-iO Dev 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.

General Dev Test Platforms

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

Issues to Verify

These issues should have either use the labels "status:ready-for-qa" or "status:ready-for-review." If it is ready for QA
then close the issue if fixed. If ready for review then leave open and assign back to the developer.

Link(s)


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
Copy link
Contributor

ariel-phet commented Dec 9, 2020

Some space appears to be freeing up in QA and this dev test would be a good shake down of a few aspects related to Pan and Zoom. However there are currently several blocking issues noted in the next comment

@pixelzoom
Copy link
Contributor Author

Re publishing a dev version... I noted that there are 3 blocking issues.

2 issues are related to PhET-iO support for pan & zoom:

Those issues seem relevant to Natural Selection, given the need to test phetsims/natural-selection#219.

1 issue is related to "key events" (I'm not familiar with this):

I contacted @ariel-phet on Zoom. He agrees that these are likely blocking for Natural Selection, and will contact @jessegreenberg .

@pixelzoom pixelzoom assigned ariel-phet and unassigned pixelzoom Dec 9, 2020
@ariel-phet ariel-phet removed their assignment Dec 9, 2020
@ariel-phet
Copy link
Contributor

This issue should also be tied to this test: phetsims/scenery#1079

@pixelzoom
Copy link
Contributor Author

This issue has been deferred for so long that the issue template has probably evolved, and most (all?) of the above comments are no longer relevant. So I'm going to close this issue, and create a new one for the 1.3.0-dev.1 dev test.

QA Pipeline automation moved this from Upcoming Tests (by priority) to Done Apr 5, 2021
@pixelzoom pixelzoom removed this from Done in QA Pipeline Apr 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA:dev-test Dev test before an RC status:on-hold
Projects
None yet
Development

No branches or pull requests

2 participants