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: Vector Addition 1.0.0-rc.2 #451

Closed
9 tasks done
pixelzoom opened this issue Nov 4, 2019 · 3 comments
Closed
9 tasks done

RC test: Vector Addition 1.0.0-rc.2 #451

pixelzoom opened this issue Nov 4, 2019 · 3 comments

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Nov 4, 2019

@KatieWoe, @arouinfar, vector-addition/1.0.0-rc.2 is ready for RC testing.

This release does not include PhET-iO or a11y.

Document issues in https://github.com/phetsims/vector-addition/issues and link to this issue.

Assigning to @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 or AM if it not there.
  • If this is rc.1 please do a memory test.
  • When making an issue, check to see if it was in a previously published version
  • If there is a console available, check for errors and include them in the Problem Description.

Focus and Special Instructions

This RC does not require a full test matrix. You can spot check the issues in "Issues to Verify" on a subset of supported platforms.

Issues to Verify

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 Nov 4, 2019

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

  • Mac 10.15 chrome
  • Mac 10.15 safari

  • Win 7 IE
  • Mac 10.12 safari

  • ChromeOS
  • iPadOS 13

@KatieWoe
Copy link
Contributor

KatieWoe commented Nov 5, 2019

QA is done

@KatieWoe KatieWoe assigned pixelzoom and unassigned KatieWoe Nov 5, 2019
@pixelzoom
Copy link
Contributor Author

🎉 Thank you @KatieWoe and QA team! Proceeding to publication of 1.0.0.

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