Replies: 4 comments
-
+1 This feature would make me (and others, I'm sure) much more likely to take the time to eval this tool. |
Beta Was this translation helpful? Give feedback.
-
It seems that Captures does that already, but it isn't clearly documented. The example shows how to use it in a URL but is it possible to use it in a JSON body? |
Beta Was this translation helpful? Give feedback.
-
Hey, thanks for your question and ideas! You can capture content from response like this: captures:
id:
jsonpath: $.id Then use it in consequent steps as a value, by using variables like: I'd also add, that the implementation for variable parsing is far from perfect and could be improved Anyways, thanks for your input! We hope you would enjoy Step CI as much as we do 😄 |
Beta Was this translation helpful? Give feedback.
-
Hi @cweekly and @fmalk |
Beta Was this translation helpful? Give feedback.
-
Hi there,
I posted on HN that I worked on a similar project in the past, it had the same runner idea and YAML format ideas. I'd love to contribute to this project since it runs smoothly than mine (I had a mocha injection system to run the tests).
Anyway, this project could benefit from one of my ideas, which is to use steps as a sequence of tests, and each test could use the result of a previous test/step - so an API flow could be followed. As an example, you might want to POST an object and then test the DELETE endpoint, with a user who has permission and another flow were a user doesn't have it.
If you guys are open to that suggestion, I'd work on it as a PR. What do you think?
Beta Was this translation helpful? Give feedback.
All reactions