-
Notifications
You must be signed in to change notification settings - Fork 462
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
Allow k6 scenario to be defined within k6 test #1797
base: master
Are you sure you want to change the base?
Allow k6 scenario to be defined within k6 test #1797
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1797 +/- ##
==========================================
+ Coverage 89.80% 89.82% +0.02%
==========================================
Files 71 71
Lines 19587 19621 +34
==========================================
+ Hits 17588 17622 +34
Misses 1999 1999 ☔ View full report in Codecov by Sentry. |
…fix/k6-scenario-within-k6-test
…fix/k6-scenario-within-k6-test
Hi, I have fixed up the tests and improved code coverage. All checks are now passing, thanks. |
Can someone please review this? Thanks |
Hi, are any maintainers able to review this PR please? |
set dev version to 0.0.1-DEV to allow local install
…fix/k6-scenario-within-k6-test
…enpearson84/taurus into fix/k6-scenario-within-k6-test
Any maintainers able to review this PR please? |
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.
Reviewed changes and tested changes in local environment.
Allow for load scenario to be defined within the K6 script as well as in the Taurus yml file. Currently if no iterations is defined in the Taurus scenario then only 1 iteration is executed before the test ends. This change adds k6 its own get-load method to allow for infinite iterations.
Closes #1791