phetsims/qa

RC Spot check: Collision Lab 1.1.0-rc.4

Closed this issue · 4 comments

jonathanolson commented

@kathy-phet, @arouinfar, collision-lab/1.1.0-rc.4 is ready for RC testing. Document issues in https://github.com/phetsims/collision-lab/issues and link to this
issue.

This is a spot test, specifically for phetsims/collision-lab#184 and determining if it caused any other physics regressions. The changes mainly deal with how almost-parallel-motion balls are handled. This is platform-agnostic, so no platform coverage is needed.

Assigning to @kathy-phet and @KatieWoe 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.
  • Test the Game Up harness on at least one platform.
  • 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
  • Try to include version numbers for browsers
  • If there is a console available, check for errors and include them in the Problem Description.
  • As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if
    there is a problem.

Issues to Verify

These issues should have the "status:ready-for-qa" 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 and link back to this issue. If the label is
"status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if 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 commented
  • Win 10 Chrome (Time = 2.5 hr )
  • Win 10 Firefox (Time = 3.5 hr)
  • MacOS 11 Safari (Time = 1 hr)
  • iPadOS 14 (Time = 1 hr)
  • ChromeOS (Time = )
KatieWoe commented

QA is done

KatieWoe commented

Matthew Moore and Steele Dalton should be added to QA credits

jonathanolson commented

Sounds good, thanks! I've added the credits, and I'm going to move forward with the production deploy!