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

Dev Test: my-solar-system 1.1.0-dev.9 #927

Closed
10 of 11 tasks
AgustinVallejo opened this issue Apr 5, 2023 · 3 comments
Closed
10 of 11 tasks

Dev Test: my-solar-system 1.1.0-dev.9 #927

AgustinVallejo opened this issue Apr 5, 2023 · 3 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@AgustinVallejo
Copy link

AgustinVallejo commented Apr 5, 2023

Dev Test

Mentions: @KatieWoe and @kathy-phet

Simulation links

Test Matrix

Please include all (non-screen reader) feature testing in these records if applicable.

  • Latest macOS, Safari (Time = 3.75hrs)
  • Windows 10, Chrome (Time = 3.00)
  • Windows 10/11, Firefox (Time = 1.5) windows 10
  • Latest iOS, Safari (Time = 3)
  • Windows 11, Chrome (Time = 4.75)

Light testing, or optionally skip if time crunch:

  • Latest macOS, Chrome (Time = 1.75hr)
  • Latest Chrome OS, Chrome (Time = )

Features included

  • Alternative Input
  • UI Sound
  • Sonification

Focus and Special Instructions

Issues to Verify

These issues should have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.


For QA...

General features

What to Test

  • Click every single button.
  • 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.
  • Try to include browser version numbers
  • If there is a console available, check for errors and include them in the Problem Description.
  • Run through the string tests on at least one platform, especially if it is about to go to rc.
  • Check the Game Up harness on one platform.

Accessibility features

What to Test

  • Specific instructions can be found above.

  • Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
    a list of features that may be supported in this test:

    • Alternative Input
    • Interactive Description
    • Sound and Sonification
    • Pan and Zoom
    • Mobile Description
  • Test all possible forms of input.

    • Test all mouse/trackpad inputs.
    • Test all touchscreen inputs.
    • Test all keyboard navigation inputs (if applicable).

Keyboard Navigation

This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.

Magnification

This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.


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

Memory test looks ok:
mem

@KatieWoe
Copy link
Contributor

Chrome book performance looked ok. There were a few instances of brief lag, but not much, and nothing I would worry about.

@KatieWoe
Copy link
Contributor

Calling QA here

@KatieWoe KatieWoe moved this to Done in QA Pipeline Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA:dev-test Dev test before an RC
Projects
Status: Done
Development

No branches or pull requests

3 participants