-
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: Capacitor-Lab-Basics 1.7.0-rc.8 #588
Comments
Spot check platforms:
|
Changing this to top priority to get @Denz1994 issues to comment on or resolve before he leaves. Please prioritize this test. |
I don't think this is an issue, but recording here. @Denz1994 or @arouinfar let me know if you want an issue. |
@KatieWoe it sounds like the numbers are shifting slightly which is to be expecting because we aren't using a monospaced font. If that's the case, no need for an issue. If the numbers are bouncing out of bounds or doing something really buggy looking, please open an issue. |
@arouinfar not out of bounds. It was sometimes more than I expected, but it was hard to replicate. Like I said, I don't really think it needs an issue. |
QA is done |
There are five issues in the repo that need attention before the upcoming release, and most are trivial. I've commented in the issues, but to summarize:
|
Thanks! I've got them on my radar, will be working on it! |
@ariel-phet , @arouinfar , Capacitor-Lab-Basics/1.7.0-rc.8 is ready for RC a spot check. Document issues in https://github.com/phetsims/capacitor-lab-basics/issues and link to this
issue. This RC should fit into the active test queue when possible. There are several issues to verify being that this sim has gone through several RC tests already. The version number doesn't match the number of RC tests due to some intermediate RC builds that didn't get tested.
I'd advise treating this test as a spot check to verify the outstanding issues listed below.
Assigning to @ariel-phet for prioritization.
General RC Test
What to Test
for a list of query parameters.)
spreadsheet and notify AR or AM if it not there.
there is a problem.
Focus and Special Instructions
Please pay close attention to the top plate charge on the second screen, specifically as detailed in this issue.
Issues to Verify
These issues should have the "status:ready-for-qa" 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 and link back to this issue. If the label is
"status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if 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: