-
Notifications
You must be signed in to change notification settings - Fork 8
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
Comments
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 |
@pixelzoom The provided old url to test the diff wrapper doesn't show any api differences. Is this correct? |
@KatieWoe asked:
Definitely NOT correct. Tracking in phetsims/natural-selection#271. |
Good to know! Seemed odd so I wanted to check. Glad it was caught. |
QA is done |
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. |
The next RC test has started, see #643. Closing. |
@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
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
sure the simulation loads without crashing or throwing errors.
Further instructions in QA Book
?phetioDebug
on the Studio and State wrapper.index.html
by double clicking it on your desktop or in a finder-view.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:
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:
The text was updated successfully, but these errors were encountered: