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: Blackbody Spectrum 1.0.0-dev.13 #285

Closed
7 tasks done
arnabp opened this issue Feb 12, 2019 · 2 comments
Closed
7 tasks done

Dev test: Blackbody Spectrum 1.0.0-dev.13 #285

arnabp opened this issue Feb 12, 2019 · 2 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@arnabp
Copy link

arnabp commented Feb 12, 2019

@ariel-phet, @DianaTavares, blackbody-spectrum/1.0.0-dev.13 is ready for dev testing. This is a test of the PhET brand only; PhET-iO is not included.

Document issues in https://github.com/phetsims/blackbody-spectrum/issues and link to this issue.

Assigning @ariel-phet for prioritization.

General Dev Test

What to Test

  • Click every single button.
  • Make sure you can't lose anything.
  • Play with the sim normally.
  • Try to break the sim.

Issues to Verify

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.


@KatieWoe
Copy link
Contributor

KatieWoe commented Feb 25, 2019

As a general note, performance on IE and Edge are rather poor.

@KatieWoe
Copy link
Contributor

QA is done.

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