-
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 Spot Check: States of Matter 1.1.0-rc.3 #212
Labels
Comments
@jbphet let me know if this list works for you. Anything not marked full is a partial test.
|
@ariel-phet for priority |
Note: Tested phetsims/states-of-matter#234 on chrome win 10. May be useful for another tester to check a different browser/platform. |
Edge performance is poor. Issue is present in published version. |
QA is done @jbphet |
Thanks QA team! I'll take it from here, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@KatieWoe and @ariel-phet, States of Matter 1.1.0-rc.3 is ready for RC testing. Testing on 1.1.0-rc.1 and 110-rc.2 has already been done, and was quite thorough, and this is the follow up test. A full test on all platforms is not necessary, just verification of the resolved issues and spot testing on key platforms. See the list of issues below for guidance on what should be tested.
Please document any issues found in https://github.com/phetsims/states-of-matter/issues and link to this issue.
Assigning @KatieWoe.
General RC Test
What to Test
Versus the last RC, the only changes are related to the issues listed below, so that can be the focus of the testing. Having said that, this is a very popular sim, so enough testing should be done to make sure that this particular release is stable enough to replace the currently published version.
Issues to Verify
The SOM-specific issues should have the "status:fixed-pending-testing" label. Check these issues off and change their status to fixed-awaiting-deploy if resolved. Otherwise, post a comment in the issue saying that it wasn't fixed.
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: