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: Energy Forms and Changes 1.0.0-dev.16 #263

Closed
4 tasks done
chrisklus opened this issue Jan 18, 2019 · 2 comments
Closed
4 tasks done

Dev test: Energy Forms and Changes 1.0.0-dev.16 #263

chrisklus opened this issue Jan 18, 2019 · 2 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@chrisklus
Copy link

chrisklus commented Jan 18, 2019

@jbphet, @arouinfar, @KatieWoe, @ariel-phet, energy-forms-and-changes/1.0.0-dev.16 is ready for dev testing. There is a hard deadline of January 31st (it's a Google sim). Please document issues in https://github.com/phetsims/energy-forms-and-changes/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.

Focus and Special Instructions

Please focus on the biggest/worst issues first. The deadline for this sim is coming up soon, so we will not be able to fix everything before 1.0 is released.

Speed control has been removed from this version, but you can bring it back for testing with showSpeedControls query param. This is useful for testing, but we are not testing for issues only caused by fast forward.

General Dev Test Platforms

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

Link


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

QA is done

@KatieWoe KatieWoe assigned jbphet and chrisklus and unassigned KatieWoe Jan 22, 2019
@jbphet
Copy link
Contributor

jbphet commented Jan 23, 2019

Thanks for the testing, @chrisklus and I will follow up on the issues.

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