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: Mean: Share and Balance 1.1.0-dev.7 #1105

Closed
15 of 19 tasks
marlitas opened this issue Jul 8, 2024 · 8 comments
Closed
15 of 19 tasks

Dev Test: Mean: Share and Balance 1.1.0-dev.7 #1105

marlitas opened this issue Jul 8, 2024 · 8 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@marlitas
Copy link

marlitas commented Jul 8, 2024

Dev Test

Mentions: @jbphet @marlitas @amanda-phet

Simulation links

Test Matrix

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

  • Latest macOS, Safari (Time = 2hrs)
  • Latest iOS, Safari (Time = 1)
  • Windows 10/11, Firefox (Time = 3.5)
  • Windows 11, Chrome (Time =2.5 )
  • Latest Chrome OS, Chrome (Time = 2hrs)

Light testing, or optionally skip if time crunch:

  • Latest macOS, Chrome (Time = )
  • Windows 10, Chrome (Time = )

If PhET-iO is being tested:

  • Latest macOS, Safari (Time = 3hrs)
  • Windows 10, Chrome (Time = 2hrs)
  • Windows 10/11, Firefox (Time =3.5 )
  • Latest iOS, Safari (Time = 1)
  • Windows 11, Chrome (Time =3)

Features included

  • PhET-iO
  • Dynamic Locale
  • Alternative Input
  • UI Sound
  • Sonification
  • Description
  • Voicing

Focus and Special Instructions

Mean: Share and Balance has had it's first screen published as a prototype and has gone through a dev-lite test. Everything is fair game.

Issues to Verify

No issues to verify.


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.

PhET-iO features

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.

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
    • Voicing
  • Test all possible forms of input.

    • Test all mouse/trackpad inputs.
    • Test all touchscreen inputs.
    • Test all keyboard navigation inputs (if applicable).
    • Test all forms of input with a screen reader (if applicable).

Screen Readers

This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

  • Windows 10 + Latest Chrome + Latest JAWS
  • Windows 10 + Latest Firefox + Latest NVDA
  • macOS + Safari + VoiceOver
  • iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information

We are tracking known screen reader bugs in
here. If you find a screen reader bug,
please check it against this list.

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.


@marlitas marlitas changed the title Dev Test: Mean: Share and Balance 1.1.0-dev. Dev Test: Mean: Share and Balance 1.1.0-dev.7 Jul 8, 2024
@marlitas marlitas added the QA:dev-test Dev test before an RC label Jul 8, 2024
@github-project-automation github-project-automation bot moved this to Upcoming Tests (by priority) in QA Pipeline Jul 8, 2024
@Nancy-Salpepi Nancy-Salpepi moved this from Upcoming Tests (by priority) to Active Tests (max 5, by priority) in QA Pipeline Jul 8, 2024
@Nancy-Salpepi
Copy link
Contributor

Wondering if there is a reason why the sim resets on the Balance Point Screen when changing the region/culture but not on the other screens. Is it because that is what happened in CaV?

@marlitas
Copy link
Author

marlitas commented Jul 9, 2024

@Nancy-Salpepi yes that's pulled over from the behavior in CaV. I actually don't think we ever discussed if we wanted to bring that behavior over to the other screens, but it does seem like it would make for a more consistent experience. I'll let @amanda-phet ultimately decide which way she wants to go with that.

@amanda-phet
Copy link
Contributor

Consistency sounds good to me!

@marlitas
Copy link
Author

marlitas commented Jul 9, 2024

Great. @Nancy-Salpepi can you create an issue?

@KatieWoe
Copy link
Contributor

KatieWoe commented Jul 9, 2024

The locale selection page looks wrong/unaligned to me.
wha

@Nancy-Salpepi
Copy link
Contributor

Nancy-Salpepi commented Jul 9, 2024

I don't see #1105 (comment) on my mac with safari, chrome or firefox.
EDIT: It was fine on FireFox 127.0.2 but then I updated and it is broken on 128.0

@KatieWoe
Copy link
Contributor

QA is done

@KatieWoe KatieWoe assigned marlitas and unassigned KatieWoe Jul 12, 2024
@KatieWoe KatieWoe moved this from Active Tests (max 5, by priority) to Dev & RC: ready for next steps in QA Pipeline Jul 12, 2024
@Luisav1 Luisav1 moved this from Dev & RC: ready for next steps to Active Tests (max 5, by priority) in QA Pipeline Jul 19, 2024
@Luisav1 Luisav1 moved this from Active Tests (max 5, by priority) to Issues To Verify in QA Pipeline Jul 19, 2024
@Luisav1 Luisav1 moved this from Issues To Verify to Dev & RC: ready for next steps in QA Pipeline Jul 19, 2024
@marlitas
Copy link
Author

All issues have been addressed. This is ready to close.

@github-project-automation github-project-automation bot moved this from Dev & RC: ready for next steps to Done in QA Pipeline Jul 23, 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

5 participants