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.3.0-dev.7 #1008

Closed
10 of 12 tasks
AgustinVallejo opened this issue Nov 30, 2023 · 4 comments
Closed
10 of 12 tasks

Dev Test: my-solar-system 1.3.0-dev.7 #1008

AgustinVallejo opened this issue Nov 30, 2023 · 4 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@AgustinVallejo
Copy link

AgustinVallejo commented Nov 30, 2023

Dev Test

Mentions: @AgustinVallejo @pixelzoom @arouinfar

Simulation links

Test Matrix

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

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

Light testing, or optionally skip if time crunch:

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

If PhET-iO is being tested:

  • Latest macOS, Safari (Time = 2.5hrs)
  • Windows 10, Chrome (Time = 2.5hrs)
  • Windows 10/11, Firefox (Time =4.5 )
  • Latest iOS, Safari (Time = 1.5)
  • Windows 11, Chrome (Time =2 )

Features included

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

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
    • Sound and Sonification
    • Pan and Zoom
  • 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 KatieWoe added the QA:dev-test Dev test before an RC label Nov 30, 2023
@pixelzoom pixelzoom changed the title Dev Test: my-solar-system 1.3.0-dev.6 Dev Test: my-solar-system 1.3.0-dev.7 Nov 30, 2023
@pixelzoom
Copy link
Contributor

@KatieWoe Since this is a dev test, we want to minimize the time between publishing the dev version and creating the 1.3 release branch. So 1.3.0-dev.7 has not been published yet. Let us know when you're ready to start, and @AgustinVallejo or I can publish.

@arouinfar
Copy link
Contributor

For PhET-iO testing, please refer to the examples.md on main, rather than the version linked from the wrapper index page. Thanks!
https://github.com/phetsims/phet-io-sim-specific/blob/main/repos/my-solar-system/examples.md

@KatieWoe
Copy link
Contributor

KatieWoe commented Dec 7, 2023

Calling QA here

@pixelzoom
Copy link
Contributor

pixelzoom commented Dec 11, 2023

Thanks QA for finding some great issues. We've addressed everything that was blocking, and are ready to proceed with RC testing.

Closing.

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