-
Notifications
You must be signed in to change notification settings - Fork 33
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
BFD-3517: Duplicate GET Locust test suites with POST #2432
BFD-3517: Duplicate GET Locust test suites with POST #2432
Conversation
@MahiFentaye Please use a little more verbosity with the PR template. |
BFD-3517_duplicate-POST-Locust-test-suites updating hashed to unhashed
fde5885
to
7567282
Compare
@MahiFentaye I think this looks good. Have you tested it? |
yes, I have tested @dondevun |
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.
Looks Good. Please update the PR template Validation section with your testing steps.
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.
Whoops, just found a typo
I think we also need to update |
…that aren't used anymore adding the new regression post test suit ti app.py BFD-3517_duplicate-POST-Locust-test-suites removing added post tests that aren't used anymore adding the new regression post test suit ti app.py
1667eb1
to
20d3b65
Compare
…ries add post high_volume_suite BFD-3517_duplicate-POST-Locust-test-suites remove unused test and queries add post high_volume_suite
20d3b65
to
67b8de3
Compare
correcting name
JIRA Ticket:
BFD-3517
What Does This PR Do?
BFD-3517_duplicate POST Locust test suites
adds
post_by_url
method that takes abody
parameterwhen
body
is present, it will make aPOST
request instead of aGET
There is a copy of each test suit to a new POST version
What Should Reviewers Watch For?
If you're reviewing this PR, please check for these things in particular:
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following:
Adds any new software dependencies
Modifies any security controls
Adds new transmission or storage of data
Any other changes that could possibly affect security?
I have considered the above security implications as it relates to this PR. (If one or more of the above apply, it cannot be merged without the ISSO or team security engineer's (
@sb-benohe
) approval.)Validation
Have you fully verified and tested these changes? Is the acceptance criteria met? Please provide reproducible testing instructions, code snippets, or screenshots as applicable.
This has been tested against test db
locust -f v2/regression_suite_post.py --users 10 --spawn-rate 10 --spawned-runtime 30s
locust -f v1/regression_suite_post.py --users 10 --spawn-rate 10 --spawned-runtime 30s
locust -f high_volume_suite_post.py --users 10 --spawn-rate 10 --spawned-runtime 30s