-
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: Atomic Interactions 1.1.0-rc.1 #216
Comments
Edge Performance: dragging the atoms and sliders shows a fair amount of lag. This tends to happen in edge, so I'm leaving it here as a comment. |
Note: This visual bug was seen on firefox, Mac 10.14. I took a picture and attempted to reproduce but have been unable to do so. As such, per @jbphet I have not made an issue. I will do so if I am able to reproduce. This comment is to record the instance to make a future issue easier to make. |
QA is done |
Thanks QA team. I'll follow up on the issues in the next RC. Closing. |
@KatieWoe, @ariel-phet, atomic-interactions/1.1.0-rc.1 is ready for RC testing. This is being done as part of the update of all sims in the States of Matter suite, so a fair amount of this code was verified during the test cycle for States of Matter 1.1.0. However, the standalone version of Atomic Interactions has additional features versus the Atomic Interactions screen in the States of Matter sim, and these features should be thoroughly tested.
Please document issues in https://github.com/phetsims/atomic-interactions/issues and link to this issue.
Assigning @ariel-phet for prioritization.
General RC Test
What to Test
Focus and Special Instructions
Much of the code that comprises this sim was tested during the recent 1.1 release of the States of Matter simulation. However, there are some differences between this sim and how the "Atomic Interactions" screen in States of Matter looks and behaves, so the testing should focus on these differences.
Issues to Verify
These issues should have the "status:fixed-pending-testing" label. Check these issues off and close them if they are fixed. 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: