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 Testing for PhET-iO Batch #718

Closed
9 of 11 tasks
samreid opened this issue Oct 26, 2016 · 7 comments
Closed
9 of 11 tasks

RC Testing for PhET-iO Batch #718

samreid opened this issue Oct 26, 2016 · 7 comments

Comments

@samreid
Copy link
Member

samreid commented Oct 26, 2016

From https://github.com/phetsims/phet-io/issues/724 we would like to RC test a large batch of PhET-iO simulations.

https://docs.google.com/spreadsheets/d/11f_g-or9NiZ12-u5JD6Y0qh1XiL0bOSLNbjXcZ5UWEo/edit?usp=sharing

  • circuit-construction-kit-black-box-study
  • function-builder (PLAYBACK ONLY)
  • proportion-playground (PLAYBACK ONLY)
@samreid
Copy link
Member Author

samreid commented Oct 26, 2016

Also assigning @ariel-phet so he is aware of this work.

@samreid
Copy link
Member Author

samreid commented Oct 26, 2016

Another recommendation for testing I forgot to mention to @phet-steele earlier. Using the "Events: colorized" test on Chrome or Firefox, make sure that each object in the simulation gives a user interface event and a nested model event. This needs to be done on one platform per sim, for each sim.

@samreid
Copy link
Member Author

samreid commented Oct 26, 2016

Also to test: In the instance proxies wrapper: do all of the objects in the simulation have a proxy in the wrapper? (i.e. is everything instrumented?)

@samreid
Copy link
Member Author

samreid commented Oct 27, 2016

Beer's Law Lab RC is ready for testing:
http://www.colorado.edu/physics/phet/dev/html/beers-law-lab/1.5.2-phetiorc.1/

@samreid
Copy link
Member Author

samreid commented Oct 27, 2016

@phet-steele please give us status updates during testing this so @zepumph can be ready with the next one when you are ready for it.

@ariel-phet
Copy link

@phet-steele should this issue remain open? Certainly the status should be changed?

@phet-steele
Copy link

This is okay to close.

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