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: Area Model Introduction 1.1.0-rc.2 #230

Closed
jonathanolson opened this issue Nov 30, 2018 · 7 comments
Closed

RC test: Area Model Introduction 1.1.0-rc.2 #230

jonathanolson opened this issue Nov 30, 2018 · 7 comments
Assignees

Comments

@jonathanolson
Copy link
Contributor

jonathanolson commented Nov 30, 2018

@kathy-phet, @amanda-phet, area-model-introduction/1.1.0-rc.2 is ready for RC testing. Document issues in https://github.com/phetsims/area-model-common/issues and link to this issue.

Assigning @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 if it not there.
  • If this is rc.1 please do a memory test.

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.


@jonathanolson
Copy link
Contributor Author

https://phet-dev.colorado.edu/html/area-model-introduction/1.1.0-rc.2/phet/area-model-introduction_en_phet.html (rc.2) should have the patch fixing iOS/etc.. Should this issue be updated to just test rc.2?

@KatieWoe
Copy link
Contributor

KatieWoe commented Dec 3, 2018

We haven't yet started on this one, so yes.

@jonathanolson jonathanolson changed the title RC test: Area Model Introduction 1.1.0-rc.1 RC test: Area Model Introduction 1.1.0-rc.2 Dec 3, 2018
@ariel-phet ariel-phet assigned KatieWoe and unassigned ariel-phet Dec 4, 2018
@KatieWoe
Copy link
Contributor

Memory Results:
Start: 25.5 MB
1 min: 35.9
2: 37.2
3: 37.8
4: 38.7
5: 38.9
6: 39.6
7: 39.5
8: 39.9
9: 39.8
10: 40.4

@jonathanolson
Copy link
Contributor Author

This release branch had patches related to phetsims/chipper#720 and phetsims/brand#34 applied since the last RC. This sim should have another RC done, if only to test the brand-related changes briefly.

@mattpen
Copy link
Contributor

mattpen commented Apr 26, 2019

This branch was patched as part of the batch maintenance release in phetsims/chipper#746. This should just have added a .gz file to the build artifacts.

@KatieWoe
Copy link
Contributor

KatieWoe commented May 1, 2019

QA is done per @ariel-phet

@jonathanolson
Copy link
Contributor Author

Thanks. I'll have another RC deploy (from new SHAs off of master) soon.

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

4 participants