Repository navigation
run: config file and login step - #24
Merged
Merged
Conversation
Options can live in traceperf.config.json (or --config file); the command line wins. A login step runs before the traffic and sends the token from its JSON response (or its cookies) with every request, so a stale token can't turn a run into a benchmark of 401 pages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
traceperf.config.json / --config; login step (token by JSON path or cookies, ${ENV} interpolation). Tests for parsing, overriding, login success, cookie, 401, missing token.