We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@jbphet, @amanda-phet, @kathy-phet, @KatieWoe number-line-distance/1.0.0-rc.1 is ready for RC testing. We're hoping to move fairly quickly on this to get it published before the school year starts. Document issues in https://github.com/phetsims/number-line-distance/issues and link to this issue.
Assigning to @kathy-phet and @KatieWoe for prioritization.
Test in order! Test the first thing first, the second thing second, and so on.
Here's a template for making issues:
<b>Test Device</b> blah <b>Operating System</b> blah <b>Browser</b> blah <b>Problem Description</b> blah <b>Steps to Reproduce</b> blah <b>Visuals</b> blah <details> <summary><b>Troubleshooting Information</b></summary> blah </details>
We typically assign the developer who opened the issue in the QA repository.
You should:
The text was updated successfully, but these errors were encountered:
Memory Test:
Sorry, something went wrong.
QA is done
kathy-phet
No branches or pull requests
@jbphet, @amanda-phet, @kathy-phet, @KatieWoe number-line-distance/1.0.0-rc.1 is ready for RC testing. We're hoping to move fairly quickly on this to get it published before the school year starts. Document issues in https://github.com/phetsims/number-line-distance/issues and link to this
issue.
Assigning to @kathy-phet and @KatieWoe 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.
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: