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.2.0-rc.3 #536

Closed
3 tasks done
jbphet opened this issue Aug 19, 2020 · 2 comments
Closed
3 tasks done

RC Spot Check: States of Matter 1.2.0-rc.3 #536

jbphet opened this issue Aug 19, 2020 · 2 comments

Comments

@jbphet
Copy link
Contributor

jbphet commented Aug 19, 2020

@KatieWoe, @ariel-phet, @arouinfar, and @kathy-phet - states-of-matter/1.2.0-rc.3 is ready for spot-check testing. This release, which includes both phet and phet-io brands and is intended to be shared with a client, addresses a handful of issues that were found during the testing of 1.2.0-rc.2. Please document issues in https://github.com/phetsims/states-of-matter/issues and link to this issue.

Assigning directly to @KatieWoe, since this is known to be a high priority.

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.

Focus and Special Instructions

This is the 2nd RC from the 1.2 branch, so the focus should be on verifying that the issues found during testing of the first RC have been adequately addressed.

Issues to Verify

See the phet-io section.

Link(s)


PhET-iO RC Test

What to Test

  • Make sure that public files do not have password protection. Use a private browser for this.
  • Make sure that private files do have password protection. Use a private browser for this.
  • Make sure standalone sim is working properly.
  • Make sure the wrapper index is working properly.
  • Make sure each wrapper is working properly.
  • Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
  • For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
    sure the simulation loads without crashing or throwing errors.
  • For an update or maintenance release please check the backwards compatibility of the playback wrapper.
    Here's the link to the previous wrapper.
  • Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:
    /wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER
    
    Further instructions in QA Book
  • Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other random platform.

Focus and Special Instructions

[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested,
list them here. Any behaviors you want QA to pay special attention to should be listed here.]

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
Copy link
Contributor

Calling an end to QA here. Issues tested and Studio hit a bit more. Rest of testing done in RC.2 earlier. If JB is satisfied with this he can move forward.

@KatieWoe KatieWoe removed their assignment Aug 20, 2020
@jbphet
Copy link
Contributor Author

jbphet commented Aug 21, 2020

Thanks @KatieWoe and team! I'll review the resultant issues and decide whether or not to publish this version. Closing.

@jbphet jbphet closed this as completed Aug 21, 2020
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

2 participants