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: Density 1.0.0-dev.11 #507

Closed
4 tasks done
jonathanolson opened this issue Jun 3, 2020 · 6 comments
Closed
4 tasks done

Dev test: Density 1.0.0-dev.11 #507

jonathanolson opened this issue Jun 3, 2020 · 6 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@jonathanolson
Copy link
Contributor

jonathanolson commented Jun 3, 2020

@DianaTavares, @ariel-phet, @kathy-phet density/1.0.0-dev.11 is ready for dev testing. Document issues in https://github.com/phetsims/density/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.
  • 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.

Focus and Special Instructions

[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested, list them here. Any behaviors you want QA to pay special attention to should be listed here.]

General Dev Test Platforms

  • Latest macOS, Chrome and Safari
  • Latest iOS, Safari
  • Windows 10, all browsers
  • Latest Chrome OS, Chrome

Link(s)


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

Currently high priority (can be done after or in concert with #506) as both are of similar priority to publish

@ariel-phet
Copy link
Contributor

Current top priority

@ariel-phet
Copy link
Contributor

bumping down to high priority so #508 can be done first.

@KatieWoe
Copy link
Contributor

Calling a close to this test, but more tests might be done while other rcs are worked out.

@KatieWoe
Copy link
Contributor

Can this be closed @jonathanolson?

@jonathanolson
Copy link
Contributor Author

Yes, sorry! Thank you.

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

3 participants