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

RC Test: gravity-force-lab-basics:1.0.0-rc.1 #429

Closed
5 tasks done
zepumph opened this issue Sep 17, 2019 · 8 comments
Closed
5 tasks done

RC Test: gravity-force-lab-basics:1.0.0-rc.1 #429

zepumph opened this issue Sep 17, 2019 · 8 comments

Comments

@zepumph
Copy link
Member

zepumph commented Sep 17, 2019

@terracoda, @emily-phet, @jessegreenberg, gravity-force-lab-basics:1.0.0-rc.1 is ready for RC testing. This is being published for the first time, and includes sound as well as PDOM descriptions. Document issues in https://github.com/phetsims/gravity-force-lab-basics/issues and link to this issue.

Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

  • Click every single button.
  • Test all possible forms of input.
    • Test all mouse/trackpad inputs.
    • Test all touchscreen inputs.
  • 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.
  • Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
  • Download HTML on Chrome and iOS.
  • Make sure the iFrame version of the simulation is working as intended on all platforms.
  • Make sure the XHTML version of the simulation is working as intended on all platforms.
  • Complete the test matrix.
  • Don't forget to make sure the sim works with Legends of Learning.
  • Check this LoL spreadsheet and notify AR or AM if it not there.
  • If this is rc.1 please do a memory test.
  • When making an issue, check to see if it was in a previously published version
  • If there is a console available, check for errors and include them in the Problem Description.

Link(s)


Accessibility (a11y) RC Test

What to Test

  • Specific instructions can be found below.
  • Make sure the a11y feature doesn't negatively affect the sim in any way.
  • 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).

Link(s)

Screen Readers

This sim supports 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 this Google Document. 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.

Final Requests


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 results look good
memresult

@KatieWoe
Copy link
Contributor

phetsims/resistance-in-a-wire#177 Occurs quite obviously when describing the mass spinners.

@KatieWoe
Copy link
Contributor

QA is done

@KatieWoe KatieWoe assigned zepumph and unassigned KatieWoe Sep 23, 2019
@zepumph
Copy link
Member Author

zepumph commented Sep 23, 2019

Thanks @KatieWoe! Closing

@jessegreenberg
Copy link
Contributor

@KatieWoe said

phetsims/resistance-in-a-wire#177 Occurs quite obviously when describing the mass spinners.

It looks like the issue is a bit different. The min value of the slider is 1000000000 and JAWS reports this as "1 zero zero zero zero zero zero zero ..." instead of reading "1 billion". Does this require further investigation?

@terracoda
Copy link
Contributor

@zepumph, is it possible to use 1 and 10 for the min and max values for the mass sliders instead of "1 000 000 000" and "10 000 000 000"?

Would that mess things up?

@terracoda
Copy link
Contributor

I'll open an issue in GFLB repo and link back to this issue.

@terracoda
Copy link
Contributor

I'll close this as we will investigate further in phetsims/gravity-force-lab-basics#181

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants