There aren’t concrete plans for scripting at this time but it’s not out of the question.
Many cases for scripting can already be solved with things like Request Chaining or custom Plugins.
Let me know if there’s something you’re trying to do that requires scripting.
Greg Schier·a year ago
@Greg Schier before postman became a beast, we started using it for integration/system testing. So most of our requests have response “assertions” to verify the correct output, and often we do a series of “GET” requests after the main test sequence so that we can check the side-effect of the tests.
Reading the plugin docs and the request chaining docs, i am not sure that either would solve our particular use case.
It should be noted that we are more interrested in “assertions” (like soapui) than we are in scripting, its just that the common “catch all” solution to assertions are based on post-request scripting. SoapUI have a different setup that allows custom assertion steps as well as just doing post-request scripts/asserts. Both approaches would help us (and I am sure there are other ways to achieve the same).
Greg Schier·a year ago
Are you looking to run these tests from within the app, or from a CLI in a CI environment?
Greg Schier·a year ago
CLI in a CI environment mostly. But we typically run the tests interactively during development of them and during troubleshooting when stuff fails….to determine if the API is broken or the test is broken mostly.
Greg Schier·a year ago
That’s great info, thanks!
Greg Schier·8 months ago
[deleted]
Greg Schier·8 months ago
I’m not sure I understand. That sounds like the perfect use for request chaining, no?
Greg Schier·8 months ago
So it's going to sound weird but I reread your comment and I have no idea what I initially understood or what I thought I initially understood from your comment. I have no explanation but I guess I'm severely lacking sleep.
Apologies, please ignore the first reply. 😭
Greg Schier·9 months ago
Allow scripting of yaak workspaces
Greg Schier·7 months ago
I’ve been using request chaining and it works for simple scenarios where the API i’m querying is well formed JSON, but I’ve ran into a subpar API (to say the least) where some of the endpoints return JSON and others return HTML 🥲
I think scripting to could be useful if I could extract some information from that response which can be a variable to inject into a subsequent request.
There aren’t concrete plans for scripting at this time but it’s not out of the question.
Many cases for scripting can already be solved with things like Request Chaining or custom Plugins.
Let me know if there’s something you’re trying to do that requires scripting.
@Greg Schier before postman became a beast, we started using it for integration/system testing. So most of our requests have response “assertions” to verify the correct output, and often we do a series of “GET” requests after the main test sequence so that we can check the side-effect of the tests.
Reading the plugin docs and the request chaining docs, i am not sure that either would solve our particular use case.
It should be noted that we are more interrested in “assertions” (like soapui) than we are in scripting, its just that the common “catch all” solution to assertions are based on post-request scripting. SoapUI have a different setup that allows custom assertion steps as well as just doing post-request scripts/asserts. Both approaches would help us (and I am sure there are other ways to achieve the same).
Are you looking to run these tests from within the app, or from a CLI in a CI environment?
CLI in a CI environment mostly. But we typically run the tests interactively during development of them and during troubleshooting when stuff fails….to determine if the API is broken or the test is broken mostly.
That’s great info, thanks!
I’m not sure I understand. That sounds like the perfect use for request chaining, no?
So it's going to sound weird but I reread your comment and I have no idea what I initially understood or what I thought I initially understood from your comment. I have no explanation but I guess I'm severely lacking sleep.
Apologies, please ignore the first reply. 😭
I’ve been using request chaining and it works for simple scenarios where the API i’m querying is well formed JSON, but I’ve ran into a subpar API (to say the least) where some of the endpoints return JSON and others return HTML 🥲
I think scripting to could be useful if I could extract some information from that response which can be a variable to inject into a subsequent request.
Thoughts how I could achieve this?