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: Gravity Force Lab: Basics 1.0.0-dev.26 #199

Closed
4 tasks done
mbarlow12 opened this issue Oct 3, 2018 · 3 comments
Closed
4 tasks done

Dev test: Gravity Force Lab: Basics 1.0.0-dev.26 #199

mbarlow12 opened this issue Oct 3, 2018 · 3 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@mbarlow12
Copy link

mbarlow12 commented Oct 3, 2018

@arouinfar, @jessegreenberg @emily-phet, gravity-force-lab-basics/1.0.0-dev.26 is ready for dev testing. Document issues in https://github.com/phetsims/gravity-force-lab-basics/issues and link to this issue.

Assigning @ariel-phet for prioritization.

General Dev Test

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.

General Dev Test Platforms

  • Latest macOS, Chrome & Safari
  • Latest iOS, Safari
  • Windows 10, Chrome & FireFox
  • Latest Chrome OS, Chrome

Link(s)


Accessibility (a11y) Dev Test

What to Test

  • Specific instructions can be found below.
  • Make sure the a11y feature doesn't negatively affect the sim in any way.
  • There's currently no assistive text available for this sim, so testing should be restricted to just keyboard navigation.

Link(s)

Keyboard Navigation

This sim supports keyboard navigation. Please make sure it works as intended on all platforms.

Focus and Special Instructions

In some previous testing for Coulomb's Law, there was a issue with lag and some odd behavior when dragging the ruler with the keyboard in Firefox (see phetsims/coulombs-law#41). This would be something to double-check for Gravity Force Lab: Basics.
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.


@ariel-phet
Copy link
Contributor

@KatieWoe this sim is close to being ready for an RC so making this a high priority since it would be nice to publish this sim soon.

@KatieWoe
Copy link
Contributor

KatieWoe commented Oct 5, 2018

QA is done

@KatieWoe KatieWoe removed their assignment Oct 5, 2018
@mbarlow12
Copy link
Author

mbarlow12 commented Oct 11, 2018

Once phetsims/gravity-force-lab-basics#72 is handled, we should be able to move on to RC testing.

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
None yet
Development

No branches or pull requests

4 participants