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: Blackbody Spectrum 1.0.0-rc.1 #328

Closed
arnabp opened this issue May 29, 2019 · 3 comments
Closed

RC Test: Blackbody Spectrum 1.0.0-rc.1 #328

arnabp opened this issue May 29, 2019 · 3 comments
Assignees

Comments

@arnabp
Copy link

arnabp commented May 29, 2019

@ariel-phet, @DianaTavares, @KatieWoe, blackbody-spectrum/1.0.0-rc.1 is ready for RC testing. This is the first RC for this sim and will need to be tested thoroughly on all platforms. Document issues in https://github.com/phetsims/blackbody-spectrum/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

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

Memory Test Results:
Start: 12.6
1 min: 18.4
2 min: 20.2
3 min: 20.0
4 min: 21.9
5 min: 22.0
6 min: 22.3
7 min: 21.0
8 min: 21.5
9 min: 22.1
10 min: 21.5

@KatieWoe
Copy link
Contributor

QA is done

@arnabp
Copy link
Author

arnabp commented Jun 18, 2019

Looks good, thanks!

@arnabp arnabp closed this as completed Jun 18, 2019
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

3 participants