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

Function Builder: dev testing (round 3) #628

Closed
pixelzoom opened this issue Jun 24, 2016 · 4 comments
Closed

Function Builder: dev testing (round 3) #628

pixelzoom opened this issue Jun 24, 2016 · 4 comments
Assignees
Labels

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Jun 24, 2016

The focus for this round of testing is the newly-implemented "Mystery" screen. It would be peachy to have this task completed by Wednesday, 6/29/16.

The dev version for testing is:

http://www.colorado.edu/physics/phet/dev/html/function-builder/1.0.0-dev.67/function-builder_en.html

Some terminology specific to the "Mystery" screen, useful for communicating about issues:

• The Mystery screen has 3 "scenes", controlled by the radio buttons at bottom center. Each scene has a different number of functions in the builder.
• A "challenge" is a set of 1 or more functions shown in the builder. The user's tasks is to guess the function(s) in the challenge.
• Each scene has a "pool" of challenges. The pools are shown in MysteryChallenges.js.
• The "generate" button is the yellow button centered below the builder. Pressing it selects a challenge randomly from the pool.
• The "reveal" buttons are the toggle buttons below the functions in the builder (they have eyeball icons on them). Pressing a "reveal" button shows/hides the identity of the function directly above it. These buttons are initially disabled for a challenge. They are enabled when the output carousel contains 3 cards, and they remain enabled until a new challenge is generated.
• The "See Inside" check box is at the lower right, and controls whether the "see inside" windows are visible on the builder. This check box is initially disabled for a challenge. It is enabled when the output carousel contains 1 card, and it remains enabled until a new challenge is generated.

Sim-specific query parameters that you may find useful when testing:

showAnswer - shows the answer to each challenge directly below the "generate" button
playAll - cycles through all challenges in the order that they appear in the challenge "pool"
populateOutput - puts 1 of each card in the output carousel on startup, on Reset All, and when generating a new challenge
slow - reduces animation speed to 25% of normal, useful for testing multitouch
testScreen - adds a "Test" screen that shows the color palette used for mystery functions

Other useful info:

• You should never see the same challenge twice in a row.
• All of the challenges will be exhausted before any are repeated.
• You should never see the same colors used for functions twice in a row.
• When the sim starts or is reset, the default challenge for each scene is always the same (the first challenge in the pool), and uses the same function colors. (This provides the teacher with a reproducible starting point, and will be described in the Teacher Tips.)

Let me know if you have any questions. Thanks!

@pixelzoom
Copy link
Contributor Author

pixelzoom commented Jun 24, 2016

I should also note that the majority of my testing of the Mystery screen has been on Mac OS X, with Chrome and Safari. I don't like passing the sim on to QA without having thoroughly tested it on other platforms myself, but I just plain ran out of time. Of particular interest are iPad, Edge and Firefox - they definitely haven't gotten enough testing love from me.

@pixelzoom
Copy link
Contributor Author

Please mention this issue in any issues that are created, so that they will be summarized here.

@phet-steele
Copy link

@pixelzoom this has been tested on many platforms (including the potentially problematic Edge & iPad) and we haven't found a single thing wrong with it. Fantastic work, I await the next iteration.

@phet-steele phet-steele removed their assignment Jun 24, 2016
@pixelzoom
Copy link
Contributor Author

Awesome, fantastic news. Thank you @phet-steele and QA team!

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants