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 for Fractions: Equality 1.0.0-dev.7 #251

Closed
4 tasks done
jonathanolson opened this issue Jan 4, 2019 · 5 comments
Closed
4 tasks done

Dev test for Fractions: Equality 1.0.0-dev.7 #251

jonathanolson opened this issue Jan 4, 2019 · 5 comments
Assignees
Labels
QA:dev-test Dev test before an RC

Comments

@jonathanolson
Copy link
Contributor

jonathanolson commented Jan 4, 2019

@amanda-phet, @ariel-phet, @kathy-phet, fractions-equality/1.0.0-dev.7 is ready for dev testing. There is a hard deadline of January 31st (it's a Google sim). Document issues in https://github.com/phetsims/fractions-common/issues and link to this issue.

Special Note
@KatieWoe this sim includes "Fraction Matcher" as the game. The game need not be thoroughly tested as very little code for that game has been touched. Fraction matcher will be getting revisited soon, but for this dev test, the game should generally be given a quick run through to make sure nothing is broken, but the game in this particular sim does should not need to be "banged on" very hard.

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.

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

@KatieWoe current top priority

I know @phet-steele has interest in dev testing these sims so also assigning him

@ghost
Copy link

ghost commented Jan 4, 2019

fraction-suite-memory-test

@ghost
Copy link

ghost commented Jan 4, 2019

Minute MB
0 27.8
1 65.0
2 79.7
3 75.1
4 72.1
5 77.2
6 73.8
7 78.5
8 74.2
9 75.4
10 77

@KatieWoe
Copy link
Contributor

KatieWoe commented Jan 8, 2019

QA is done

@jonathanolson
Copy link
Contributor Author

Thanks!

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