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: Wave Interference 1.0.0-dev.51 #238

Closed
4 tasks done
samreid opened this issue Dec 12, 2018 · 6 comments
Closed
4 tasks done

Dev test: Wave Interference 1.0.0-dev.51 #238

samreid opened this issue Dec 12, 2018 · 6 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@samreid
Copy link
Member

samreid commented Dec 12, 2018

@ariel-phet and @KatieWoe, Wave Interference 1.0.0-dev.51 is ready for the first round of dev testing. This sim has a publication deadline of Jan 31, 2019 but will be great to complete sooner because other sims share the same deadline. The dev test should focus on searching for buggy or sim breaking behavior. This is a PhET Brand sim and does not require PhET-iO testing.

Please document issues in https://github.com/phetsims/wave-interference/issues. Assign issues to @samreid and link them back to this QA issue.

Per @ariel-phet's direction, I'm labeling top priority and assigning to Katie.

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.

Focus and Special Instructions

In addition to the general QA Dev testing, please test crashing conditions on iPad 2. How long can you use the sim before it crashes? Does any particular conditions lead to crashing? Please test multiple trials and report results at phetsims/wave-interference#128. Per @ariel-phet's direction, take a little bit of time exploring this, but not too long.

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

Memory Test Results:
Start: 59.2 MB
1 min: 67.3 MB
2 min: 68.6 MB
3 min: 69.1 MB
4 min: 69.6 MB
5 min: 69.9 MB
6 min: 70.4 MB
7 min: 70.5 MB
8 min: 70.9 MB
9 min: 71.1 MB
10 min: 71.2 MB

@KatieWoe
Copy link
Contributor

QA is done @samreid

@KatieWoe KatieWoe assigned samreid and unassigned KatieWoe Dec 14, 2018
@samreid
Copy link
Member Author

samreid commented Dec 15, 2018

Thanks @KatieWoe, @lmulhall-phet @JRomero0613! Since all other open issues are marked in the Wave Interference repo, we can use that as our to-do list and close this issue.

@samreid samreid closed this as completed Dec 15, 2018
@samreid
Copy link
Member Author

samreid commented Dec 15, 2018

Reopening to double check on phetsims/wave-interference#128 (comment)

@samreid samreid reopened this Dec 15, 2018
@samreid samreid assigned KatieWoe and unassigned samreid Dec 15, 2018
@KatieWoe
Copy link
Contributor

@KatieWoe KatieWoe assigned samreid and unassigned KatieWoe Dec 17, 2018
@samreid
Copy link
Member Author

samreid commented Dec 17, 2018

Thanks @KatieWoe, closing.

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

2 participants