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: Capacitor-Lab-Basics 1.7.0-rc.8 #588

Closed
4 tasks done
Denz1994 opened this issue Dec 17, 2020 · 8 comments
Closed
4 tasks done

RC Test: Capacitor-Lab-Basics 1.7.0-rc.8 #588

Denz1994 opened this issue Dec 17, 2020 · 8 comments

Comments

@Denz1994
Copy link
Contributor

Denz1994 commented Dec 17, 2020

@ariel-phet , @arouinfar , Capacitor-Lab-Basics/1.7.0-rc.8 is ready for RC a spot check. Document issues in https://github.com/phetsims/capacitor-lab-basics/issues and link to this
issue. This RC should fit into the active test queue when possible. There are several issues to verify being that this sim has gone through several RC tests already. The version number doesn't match the number of RC tests due to some intermediate RC builds that didn't get tested.

I'd advise treating this test as a spot check to verify the outstanding issues listed below.

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

Please pay close attention to the top plate charge on the second screen, specifically as detailed in this issue.

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

KatieWoe commented Dec 17, 2020

Spot check platforms:

  • Win 10 Chrome
  • Win 10 Firefox
  • MacOS 11 Safari
  • iPadOS 14 Safari
  • ChromeOS

@kathy-phet
Copy link

Changing this to top priority to get @Denz1994 issues to comment on or resolve before he leaves. Please prioritize this test.

@KatieWoe
Copy link
Contributor

I don't think this is an issue, but recording here. @Denz1994 or @arouinfar let me know if you want an issue.
On ChromeOS, when numbers are changing, they can bounce around when width changes. Seen when looking at voltage during discharge or when timer is running. Can be hard to record.

@arouinfar
Copy link
Contributor

@KatieWoe it sounds like the numbers are shifting slightly which is to be expecting because we aren't using a monospaced font. If that's the case, no need for an issue. If the numbers are bouncing out of bounds or doing something really buggy looking, please open an issue.

@KatieWoe
Copy link
Contributor

@arouinfar not out of bounds. It was sometimes more than I expected, but it was hard to replicate. Like I said, I don't really think it needs an issue.

@KatieWoe
Copy link
Contributor

QA is done

@arouinfar
Copy link
Contributor

arouinfar commented Jan 15, 2021

There are five issues in the repo that need attention before the upcoming release, and most are trivial. I've commented in the issues, but to summarize:

@arouinfar arouinfar assigned jonathanolson and unassigned arouinfar and Denz1994 Jan 15, 2021
@jonathanolson
Copy link
Contributor

Thanks! I've got them on my radar, will be working on it!

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

6 participants