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-Lite Test: CODAP + PDL 1.1.0-dev.3 #1096

Closed
3 of 9 tasks
matthew-blackman opened this issue Jun 14, 2024 · 2 comments
Closed
3 of 9 tasks

Dev-Lite Test: CODAP + PDL 1.1.0-dev.3 #1096

matthew-blackman opened this issue Jun 14, 2024 · 2 comments
Assignees
Labels
QA:dev-lite Early, short dev test

Comments

@matthew-blackman
Copy link

matthew-blackman commented Jun 14, 2024

Dev-Lite Test

Mentions: @samreid @catherinecarter

Simulation links

Test Matrix

  • Tester 1 (Tester = KW, Platform = Win 11 Chrome, Time = 2{max 2 hours}
  • Tester 2 (Tester = NS, Platform = mac + safari , Time = 2{max 2 hours}

Features included

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

Focus and Special Instructions

Please test the following:

  1. Collecting data for each of the available variables across all screens
  2. Checking and unchecking variables in the sidebar menu attached to the sim
  3. Deleting variables by clicking the column on the CODAP table
  4. Various combinations of 2 and 3 listed above
  5. Checking/unchecking variables after some data has already been collected - Data should not be collected for a variable unless its box is checked when the projectile lands
  6. Confirm that clicking save/export/make a copy in the CODAP menu will save the entire combined state of the sim + CODAP integration

Issues to Verify

There are no known 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.


@Nancy-Salpepi
Copy link
Contributor

FYI @matthew-blackman --CODAP crashed a couple of times for me. I have no idea why and haven't been able to reproduce at all.

@KatieWoe
Copy link
Contributor

Calling QA here

@KatieWoe KatieWoe moved this from Active Tests (max 5, by priority) to Dev & RC: ready for next steps in QA Pipeline Jun 20, 2024
@github-project-automation github-project-automation bot moved this from Dev & RC: ready for next steps to Done in QA Pipeline Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA:dev-lite Early, short dev test
Projects
Status: Done
Development

No branches or pull requests

4 participants