-
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: Coulomb's Law 1.0.0-rc.7 #242
Comments
@mbarlow12 how does this list look for platforms?
|
I'm checking platforms off in the list above if they pass all RC test measures and pre-existing issue checks, EXCEPT for this (quite problematic) bug Laura found above (phetsims/coulombs-law#97). In other words, a check means that new bug is there, but everything else is performing perfectly fine. |
New RC version at: Apologies for the issue; single line comment prevented redrawing the vectors and force values. |
QA Testers: Please test the link above. |
We can also close this and use #243. |
Closing. |
@KatieWoe, @arouinfar, @jessegreenberg, @ariel-phet coulombs-law/1.0.0-rc.8 is ready for a final spot RC check. Document issues in https://github.com/phetsims/coulombs-law/issues and link to this issue.
There are a few issues discovered from the last RC that won't be addressed prior to this publication. They are noted below.
Assigning @ariel-phet for prioritization.
General RC Test
What to Test
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.
iOS crashing is apparently no longer an issue, but we should still check to ensure it doesn't arise again.
The following issues won't be addressed prior to publication.
Link(s)
Accessibility (a11y) RC Test
What to Test
Link(s)
Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended.
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: