You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature: Provide a converter option to insert custom K6 "setup()" logic, that will be injected during conversion.
Reasoning: K6 supports a life cycle: https://k6.io/docs/using-k6/test-life-cycle/
The package already supports the “pre-request” functionality from Postman, but it feels that “setup()” and “teardown()” is not a concept that exists in Postman, and it serves more the K6 execution.
Approach: Provide a file reference as a --k6-setup CLI parameter, that will be take the content of the file and insert it in the generated K6 script.
The text was updated successfully, but these errors were encountered:
Given I have multiple requests that required authentication.
And I execute the script with --separate true flag.
Then configured setup function that returns the correct JWT token.
How can I pass the access_token to each file requests/SAMPLE_FILE.js to be added to the headers config?
Feature: Provide a converter option to insert custom K6 "setup()" logic, that will be injected during conversion.
Reasoning: K6 supports a life cycle: https://k6.io/docs/using-k6/test-life-cycle/
The package already supports the “pre-request” functionality from Postman, but it feels that “setup()” and “teardown()” is not a concept that exists in Postman, and it serves more the K6 execution.
Approach: Provide a file reference as a --k6-setup CLI parameter, that will be take the content of the file and insert it in the generated K6 script.
The text was updated successfully, but these errors were encountered: