-
Notifications
You must be signed in to change notification settings - Fork 231
Gloss; add definition for happy path #997
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
Conversation
There's a version of the docs published here: https://mdr-ci.staging.k6.io/docs/refs/pull/997/merge It will be deleted automatically in 30 days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
: A period that lets VUs finish an iteration at the end of a load test. Graceful stops prevent abrupt halts in execution.<br/><br/>[Graceful stop reference](/using-k6/scenarios/graceful-stop/) | ||
|
||
Happy path | ||
: The default system behavior that happens when a known input produces an expected output. A common mistake in performance testing happens when scripts account only for the happy path. Most load tests try to discover system errors, so test scripts should include exception handling.<br/><br/>[Happy path (Wikipedia)](https://en.wikipedia.org/wiki/Happy_path) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
: The default system behavior that happens when a known input produces an expected output. A common mistake in performance testing happens when scripts account only for the happy path. Most load tests try to discover system errors, so test scripts should include exception handling.<br/><br/>[Happy path (Wikipedia)](https://en.wikipedia.org/wiki/Happy_path) | |
: The default system behavior that happens when a known input produces an expected output. A common mistake in performance testing happens when scripts account only for the best case (in other words, the happy path). Most load tests try to discover system errors, so test scripts should include exception handling.<br/><br/>[Happy path (Wikipedia)](https://en.wikipedia.org/wiki/Happy_path) |
To avoid using the term name in the definition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've put it in parenthesis, because I want the text to drive home how the happy path relates specifically to testing. I want to be explicit that "best case" is synonymous with "happy path". And I avoided "scenario" only because it could mean something else in this gloss :-)
part of #932