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

RC test: Natural Selection 1.3.0-rc.1 #641

Closed
4 tasks done
pixelzoom opened this issue Apr 13, 2021 · 8 comments
Closed
4 tasks done

RC test: Natural Selection 1.3.0-rc.1 #641

pixelzoom opened this issue Apr 13, 2021 · 8 comments
Assignees

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Apr 13, 2021

@KatieWoe, @kathy-phet, @amanda-phet, natural-selection 1.3.0-rc.1 is ready for RC testing. This is a full RC test, requiring testing of brands=phet,phet-io. Test matricies are required.

Publication milestone is 4/30/21.

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

Assigning to @kathy-phet and @KatieWoe 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.
  • N/A 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.

Issues to Verify

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

Link(s)


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.
  • If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
  • If filled in by issue creator, please test the diff wrapper against {{URL_TO_OLD_VERSION_ROOT}}.
  • Test that the sim works offline:

Issues to Verify

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

Additional checks

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.


@KatieWoe
Copy link
Contributor

I had the PhET brand sim crash and reload on iPadOS 14 under normal use. showPointerAreas was on, which I know can lower performance, so I didn't make an issue. If you think I should @pixelzoom let me know.

@pixelzoom
Copy link
Contributor Author

I had the PhET brand sim crash and reload on iPadOS 14 under normal use. showPointerAreas was on, which I know can lower performance, so I didn't make an issue. If you think I should @pixelzoom let me know.

If you can make it happen again (even with showPointers on), please create an issue.

@KatieWoe
Copy link
Contributor

@pixelzoom The provided old url to test the diff wrapper doesn't show any api differences. Is this correct?

@pixelzoom
Copy link
Contributor Author

@KatieWoe asked:

@pixelzoom The provided old url to test the diff wrapper doesn't show any api differences. Is this correct?

Definitely NOT correct. Tracking in phetsims/natural-selection#271.

@KatieWoe
Copy link
Contributor

Good to know! Seemed odd so I wanted to check. Glad it was caught.

@KatieWoe
Copy link
Contributor

QA is done

@pixelzoom
Copy link
Contributor Author

Thank you @KatieWoe and QA team! We'll need another spot-check RC to verify the issues that were uncovered here. I'll keep this issue open and self-assigned until that RC is rolling.

@pixelzoom
Copy link
Contributor Author

The next RC test has started, see #643.

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants