-
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.66 #264
Labels
QA:dev-test
Dev test before an RC
Comments
This was referenced Jan 22, 2019
@KatieWoe marking high priority currently. Once EFAC dev testing (current round) is complete, this sim will likely move to top priority. |
QA is done |
Thanks @KatieWoe and the entire QA team! I'll follow up in the opened issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@ariel-phet and @KatieWoe, Wave Interference 1.0.0-dev.66 is ready for the 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.
The first round of dev testing was completed in #238. Since then there have been numerous major changes in the implementation and complex new features added. This is the second round. Please be aware some issues discovered during #238 were marked as deferred.
Please document issues in https://github.com/phetsims/wave-interference/issues. Assign issues to @samreid and link them back to this QA issue.
In the prior issue #238 I was directed to label top priority and assign to Katie. Not sure whether this issue has the same priority or not, but I'll use that as a starting point. Co-assigning @ariel-phet so he can confirm scheduling, priority, etc.
General Dev Test
What to Test
Focus and Special Instructions
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:
UPDATE: I noticed other issues were already marked with top and high priority, so I'll remove the priority label until @ariel-phet can take a look.
The text was updated successfully, but these errors were encountered: