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: Buoyancy + Density + Buoyancy: Basics 1.2.0-dev.4 #1136

Closed
34 of 45 tasks
samreid opened this issue Aug 21, 2024 · 5 comments
Closed
34 of 45 tasks

Dev Test: Buoyancy + Density + Buoyancy: Basics 1.2.0-dev.4 #1136

samreid opened this issue Aug 21, 2024 · 5 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@samreid
Copy link
Member

samreid commented Aug 21, 2024

Dev Test

Mentions: @DianaTavares @kathy-phet @KatieWoe @Nancy-Salpepi @zepumph @samreid @arouinfar

Simulation links

Buoyancy

Buoyancy: Basics

Density

Test Matrix

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

For Buoyancy

  • Latest macOS, Safari (Time = 3) (Tester = NS)
  • Latest iOS, Safari (Time = 2) (Tester = NS)
  • Windows 10/11, Firefox (Time =4.5 ) (Tester = MM, KW)
  • Windows 11, Chrome (Time = 2) (Tester = MM)
  • Latest Chrome OS, Chrome (Time = 2 ) (Tester = MM)

Light testing, or optionally skip if time crunch:

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

If PhET-iO is being tested:

  • Latest macOS, Safari (Time =2.5 ) (Tester = NS)
  • Windows 10, Chrome (Time = 2.5) (Tester = CH)
  • Windows 10/11, Firefox (Time = 2.5) (Tester = KW)
  • Latest iOS, Safari (Time = 1.5) (Tester = NS)
  • Windows 11, Chrome (Time =2 ) (Tester = MM)

For Buoyancy Basics

  • Latest macOS, Safari (Time = 1.75) (Tester = NS )
  • Latest iOS, Safari (Time = 2) (Tester = AM)
  • Windows 10/11, Firefox (Time =2) (Tester =MM )
  • Windows 11, Chrome (Time = 2) (Tester = JD )
  • Latest Chrome OS, Chrome (Time = 2 ) (Tester = MM)

Light testing, or optionally skip if time crunch:

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

If PhET-iO is being tested:

  • Latest macOS, Safari (Time = 2 ) (Tester = NS)
  • Windows 10, Chrome (Time = ) (Tester = NS )
  • Windows 10/11, Firefox (Time = 2) (Tester = MM)
  • Latest iOS, Safari (Time = 1) (Tester = NS)
  • Windows 11, Chrome (Time = 1.5) (Tester = KW)

For Density

  • Latest macOS, Safari (Time = 1.5) (Tester = NS)
  • Latest iOS, Safari (Time = 1 ) (Tester = AM )
  • Windows 10/11, Firefox (Time = 2 ) (Tester =MM )
  • Windows 11, Chrome (Time = 2.5 ) (Tester = JD )
  • Latest Chrome OS, Chrome (Time =2 ) (Tester = MM)

Light testing, or optionally skip if time crunch:

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

If PhET-iO is being tested:

  • Latest macOS, Safari (Time =3 ) (Tester = NS)
  • Windows 10, Chrome (Time = 1.5 ) (Tester = NS)
  • Windows 10/11, Firefox (Time = 1) (Tester = KW)
  • Latest iOS, Safari (Time = 1 ) (Tester = AM )
  • Windows 11, Chrome (Time =2.5 ) (Tester =JD )

Features included

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

Focus and Special Instructions

We had a preliminary dev test a few months ago that found a lot of issues. The simulation is now in a much better state
and we are hopeful to address issues discovered in this dev test and move directly into RC.1. So this should be a thorough
test of all 10 screens across the 3 simulations.

Earlier versions indicated some crashing behavior during fuzzing on iPad, so we would like to request iPad testing and
see how frequently it crashes under manual usage.

We also recommend testing on iPhone to check the behavior, usage and potential crashing behavior.

Also, please test using the keyboard grab/drag interaction for blocks.

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.

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.


@samreid samreid added the QA:dev-test Dev test before an RC label Aug 21, 2024
@samreid samreid changed the title Dev Test: Buoyancy + Density + Buoyancy: Basics {{VERSION}} Dev Test: Buoyancy + Density + Buoyancy: Basics 1.2.0-dev.4 Aug 22, 2024
@Nancy-Salpepi
Copy link
Contributor

@samreid @zepumph
Is this a "won't fix" type of thing or would you like an issue?

video
Arrows.mp4

@samreid
Copy link
Member Author

samreid commented Aug 30, 2024

I recommend an issue and we should investigate, thanks!

@KatieWoe
Copy link
Contributor

KatieWoe commented Sep 4, 2024

QA is done

@KatieWoe KatieWoe assigned samreid and unassigned KatieWoe Sep 4, 2024
@samreid
Copy link
Member Author

samreid commented Sep 5, 2024

Great discoveries @Nancy-Salpepi @KatieWoe @Ashton-Morris @JaronDroder @Matthew-Moore240 and anyone else that helped. I confirmed that the remaining open issues are tracked on the project board, so we will continue there, closing.

@samreid samreid closed this as completed Sep 5, 2024
@zepumph
Copy link
Member

zepumph commented Oct 9, 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