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 Test: States of Matter 1.1.0-rc.1 #185

Closed
11 tasks done
jbphet opened this issue Sep 12, 2018 · 11 comments
Closed
11 tasks done

RC Test: States of Matter 1.1.0-rc.1 #185

jbphet opened this issue Sep 12, 2018 · 11 comments
Assignees

Comments

@jbphet
Copy link
Contributor

jbphet commented Sep 12, 2018

States of Matter 1.1.0-rc.1 is ready for release candidate (RC) testing. This release is phet brand only with no a11y. This release is motivated by a number of requests for changes to the sim, see the list of issues below for details. Please document issues in https://github.com/phetsims/states-of-matter/issues and link to this issue.

Assigning @ariel-phet for prioritization.

General RC Test

What to Test

  • Click every single button.
  • Test all possible forms of input.
    • Test all mouse/trackpad inputs.
    • Test all touchscreen inputs.
  • If there is sound, make sure it works.
  • Make sure you can't lose anything.
  • Play with the sim normally.
  • Try to break the sim.
  • Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
  • Download HTML on Chrome and iOS.
  • Make sure the iFrame version of the simulation is working as intended on all platforms.
  • Make sure the XHTML version of the simulation is working as intended on all platforms.
  • Complete the test matrix.
  • Don't forget to make sure the sim works with Legends of Learning.
  • Check this LoL spreadsheet and notify AR if it not there.

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:

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


@ariel-phet
Copy link
Contributor

@KatieWoe current top testing priority

@phet-steele
Copy link
Contributor

@KatieWoe @lmulhall-phet checkboxes cannot be marked when they are in/preceeded by markdown, for some reason. I had to take out the list of issues to verify from the collapsible section AND put it before the collapsible section (wasn't working putting it at the end of the issue). Please rethink the template or find a better solution in /issues/19.

@phet-steele
Copy link
Contributor

RE #185 (comment), see #19 (comment) and #19 (comment). We are good now, I hope.

@ghost
Copy link

ghost commented Sep 13, 2018

@jbphet, if we're planning on doing another RC, do you think we could get some query parameters that speed up the heating/cooling process?

@KatieWoe
Copy link
Contributor

@jbphet QA is done

@jbphet
Copy link
Contributor Author

jbphet commented Sep 20, 2018

Based on a discussion that occurred during the 9/20/2018 status meeting, we realized that the XHTML version had not been tested. I updated the description above to include the XHTML link, and am assigning back to QA to verify (from the sound of it, it should be a quick verification).

@KatieWoe
Copy link
Contributor

KatieWoe commented Sep 20, 2018

QA confirmed on Win 10 and Mac 10.13.

@JRomero0613
Copy link

XHTML confirmed on Mac 10.10.5, 10.11.6, and 10.12.6.

@KatieWoe
Copy link
Contributor

Confirmed on Win 7, Win 8.1, and Chrome OS

@KatieWoe
Copy link
Contributor

Confirmed on iOS 9, 10, 11, and 12. QA is done. @jbphet

@jbphet
Copy link
Contributor Author

jbphet commented Sep 24, 2018

Thanks @KatieWoe and crew! I'll address the issues individually, and we'll call this done. Closing.

@jbphet jbphet closed this as completed Sep 24, 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

5 participants