-
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: Balancing Chemical Equations 1.2.0-rc.1 #237
Comments
@KatieWoe as discussed over Slack, this sim is aiming to be republished by March. Several high priority tests are likely to come down the pipe, but potentially not until next week, so adding this to the queue, to hopefully get it done sooner than later. |
Memory Tests: |
QA is done. |
@KatieWoe , @arouinfar, @ariel-phet, Balancing Chemical Equations 1.2.0-rc.1 is ready for RC testing.
This RC is for
brand=phet
only (no PhET-io, no a11y), and it will not be provided to a client. The deadline mentioned in phetsims/balancing-chemical-equations#130 is "March", presumably 2019.Document issues in https://github.com/phetsims/balancing-chemical-equations/issues and link to this issue.
Assigning to @ariel-phet for prioritization.
General RC Test
What to Test
Focus and Special Instructions
According to phetsims/balancing-chemical-equations#130, the primary motivation for this release is ePub and LoL support. Secondary is to pick up general common-code enhancements, and sim-specific changes identified in "Issues to Verify".
Sim-specific query parameters can be found in BCEQueryParameters.
playAll
andshowReward
are both useful for testing.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: