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
Hello, I'm using har-to-k6 to test a flow in my company's app. In this flow there are multiple requests to a graphql endpoint where the endpoint url is always the same and what differs is the postData. Prior to using har-to-k6 I had the ability to add request tags which I used to add the gql operation, which would then propogate through to the json output of the k6 run.
Since the k6 script is now generated instead of hand written, I can't add these tags anymore.
I did try and add the tags onto the request body, but it seems like these params are only supported by k6/http. Is there a workaround to be able to set tags, or would that be a feature request?
The text was updated successfully, but these errors were encountered:
I did manage to work around this in the end by adding each operation as a "page" to the har file. Then set the pageref on each entry as that operation. It then comes out in the tags on the json output for the k6 run.
Would be nice to see some support for request tagging though!
Hello, I'm using har-to-k6 to test a flow in my company's app. In this flow there are multiple requests to a graphql endpoint where the endpoint url is always the same and what differs is the postData. Prior to using har-to-k6 I had the ability to add request tags which I used to add the gql operation, which would then propogate through to the json output of the k6 run.
Since the k6 script is now generated instead of hand written, I can't add these tags anymore.
I did try and add the tags onto the request body, but it seems like these params are only supported by k6/http. Is there a workaround to be able to set tags, or would that be a feature request?
The text was updated successfully, but these errors were encountered: