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

Revisit latest batch of PhET-iO sims #724

Closed
phet-steele opened this issue Nov 4, 2016 · 3 comments
Closed

Revisit latest batch of PhET-iO sims #724

phet-steele opened this issue Nov 4, 2016 · 3 comments

Comments

@phet-steele
Copy link

phet-steele commented Nov 4, 2016

It was recommended to take a quick second pass at testing the batch of PhET-iO sims in #718 and phetsims/phet-io/issues/724. This would allot time for QA to report the issues that were otherwise deemed unworthy to pursue before the deadline. These include:

  • Highlighting nodes that are not instrumented.
  • Cleaning up sliders in Instance Proxies (their ranges and worthiness to be sliders at all).

Mentioning @samreid.
@ariel-phet please prioritize, note QA would not be actively looking for bugs. I'm already expecting this work to begin, at minimum, after #721. I'm not good at making truthful time estimates, but maybe a couple days?

@ariel-phet
Copy link

@phet-steele putting at medium priority for the moment, lets focus on QA testing for a few sim (FAMB, CL:B, and soon GAO and SOM) with the understanding the GAO and SOM will take priority once those are ready. There are not too many big sim tests on the horizon after those wrap up.

@ariel-phet
Copy link

@phet-steele I think at this point this issue is quite stale. What say you? If so go ahead and close

@phet-steele
Copy link
Author

@ariel-phet I do not think this issue is stale, however developer work on resolving any issues with these sims is unlikely to happen anytime soon. By extension, I think QA time on this would be nice, but also somewhat wasted. Closing since it would be better to test when developers are ready (and it would presumably be one sim at a time, not a large batch).

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

2 participants