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

Organization and Testing for Decaf Batch #497

Closed
samreid opened this issue Apr 22, 2020 · 3 comments
Closed

Organization and Testing for Decaf Batch #497

samreid opened this issue Apr 22, 2020 · 3 comments
Assignees
Labels
priority:1-top QA:dev-test Dev test before an RC

Comments

@samreid
Copy link
Member

samreid commented Apr 22, 2020

In phetsims/decaf#79 I published a new batch of simulations for decaf testing.

In slack, @KatieWoe said:

I would make sure each could open on Win Chrome, Win Firefox, Win Edge, Win IE, Mac 15 Chrome, Mac 15 Safari, iPad 13 Safari and Chrome OS. Probably do a bit of testing on each to determine if anything is unusably slow on important platforms.

We should decide how to track the testing for these simulations. We would like to make it easy to see when a simulation is ready for publication, or, if not, what the problems are, and make it easy to deploy new versions for testing. I sketched out a spreadsheet to start the discussion.

https://docs.google.com/spreadsheets/d/10bO1Eimm5Y7TH4o7QPebpNUaIItxYK-VnKcSe24TXmc/edit#gid=0

Let's discuss organization around this testing and how to proceed. And the batch mentioned in phetsims/decaf#79 and listed again in the prototype spreadsheet is ready for testing.

@KatieWoe
Copy link
Contributor

Talked with Sam a bit already, added a device/platform, and chose what we would say about each (good, ok [meaning that it lags noticeably but doesn't hurt learning], and unusable).
Testing is underway.

@ariel-phet ariel-phet added QA:dev-test Dev test before an RC priority:1-top labels Apr 22, 2020
@ariel-phet ariel-phet removed their assignment Apr 22, 2020
@ariel-phet
Copy link
Contributor

Concurrent top priority with #494

@KatieWoe
Copy link
Contributor

Now in #499. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:1-top QA:dev-test Dev test before an RC
Projects
None yet
Development

No branches or pull requests

4 participants