-
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: Wave Interference 1.0.0-dev.51 #238
Comments
Memory Test Results: |
QA is done @samreid |
Thanks @KatieWoe, @lmulhall-phet @JRomero0613! Since all other open issues are marked in the Wave Interference repo, we can use that as our to-do list and close this issue. |
Reopening to double check on phetsims/wave-interference#128 (comment) |
Thanks @KatieWoe, closing. |
@ariel-phet and @KatieWoe, Wave Interference 1.0.0-dev.51 is ready for the first round of dev testing. This sim has a publication deadline of Jan 31, 2019 but will be great to complete sooner because other sims share the same deadline. The dev test should focus on searching for buggy or sim breaking behavior. This is a PhET Brand sim and does not require PhET-iO testing.
Please document issues in https://github.com/phetsims/wave-interference/issues. Assign issues to @samreid and link them back to this QA issue.
Per @ariel-phet's direction, I'm labeling top priority and assigning to Katie.
General Dev Test
What to Test
Focus and Special Instructions
In addition to the general QA Dev testing, please test crashing conditions on iPad 2. How long can you use the sim before it crashes? Does any particular conditions lead to crashing? Please test multiple trials and report results at phetsims/wave-interference#128. Per @ariel-phet's direction, take a little bit of time exploring this, but not too long.
General Dev Test Platforms
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: