Skip to content
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 Spot Check: States of Matter 1.1.0-rc.3 #212

Closed
3 tasks done
jbphet opened this issue Oct 26, 2018 · 6 comments
Closed
3 tasks done

RC Spot Check: States of Matter 1.1.0-rc.3 #212

jbphet opened this issue Oct 26, 2018 · 6 comments

Comments

@jbphet
Copy link
Contributor

jbphet commented Oct 26, 2018

@KatieWoe and @ariel-phet, States of Matter 1.1.0-rc.3 is ready for RC testing. Testing on 1.1.0-rc.1 and 110-rc.2 has already been done, and was quite thorough, and this is the follow up test. A full test on all platforms is not necessary, just verification of the resolved issues and spot testing on key platforms. See the list of issues below for guidance on what should be tested.

Please document any issues found in https://github.com/phetsims/states-of-matter/issues and link to this issue.

Assigning @KatieWoe.

General RC Test

What to Test

Versus the last RC, the only changes are related to the issues listed below, so that can be the focus of the testing. Having said that, this is a very popular sim, so enough testing should be done to make sure that this particular release is stable enough to replace the currently published version.

Issues to Verify

The SOM-specific issues should have the "status:fixed-pending-testing" label. Check these issues off and change their status to fixed-awaiting-deploy if resolved. 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:

  <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>

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:

  1. Consult the QA Book.
  2. Google it.
  3. Ask Katie.
  4. Ask a developer.
  5. Google it again.
  6. Cry.


@KatieWoe
Copy link
Contributor

KatieWoe commented Oct 26, 2018

@jbphet let me know if this list works for you. Anything not marked full is a partial test.

  • Win 10 chrome Full
  • Win 10 firefox
  • Win 10 edge Full

  • Mac 10.14 chrome
  • Mac 10.14 firefox Full
  • Mac 10.14 safari Full

  • iOS 12 Full

  • Chrome OS

  • Win 7 IE
  • Mac 10.11 safari

@KatieWoe
Copy link
Contributor

@ariel-phet for priority

@KatieWoe
Copy link
Contributor

Note: Tested phetsims/states-of-matter#234 on chrome win 10. May be useful for another tester to check a different browser/platform.

@KatieWoe
Copy link
Contributor

Edge performance is poor. Issue is present in published version.

@KatieWoe
Copy link
Contributor

QA is done @jbphet

@jbphet
Copy link
Contributor Author

jbphet commented Oct 29, 2018

Thanks QA team! I'll take it from here, closing.

@jbphet jbphet closed this as completed Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants