-
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
Dev test: Energy Forms and Changes 1.0.0-dev.16 #263
Labels
QA:dev-test
Dev test before an RC
Comments
QA is done |
Thanks for the testing, @chrisklus and I will follow up on the issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@jbphet, @arouinfar, @KatieWoe, @ariel-phet, energy-forms-and-changes/1.0.0-dev.16 is ready for dev testing. There is a hard deadline of January 31st (it's a Google sim). Please document issues in https://github.com/phetsims/energy-forms-and-changes/issues and link to this issue.
Assigning @ariel-phet for prioritization.
General Dev Test
What to Test
Focus and Special Instructions
Please focus on the biggest/worst issues first. The deadline for this sim is coming up soon, so we will not be able to fix everything before 1.0 is released.
Speed control has been removed from this version, but you can bring it back for testing with
showSpeedControls
query param. This is useful for testing, but we are not testing for issues only caused by fast forward.General Dev Test Platforms
Link
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: