I’ve used it in past projects and it’s a great alternative to postman, in particular it’s way more minimalist and simpler to integrate into other tools.
While this was submitted a year ago, it didn’t seem to garner much attention. Given this community’s interest in both networking and text-based tools, I thought it was worth another mention.
If I’m playing around with a new web API I usually build up a little library of utility code for setting the correct headers, building URLs, creating request content, etc. Then I can play around making requests, inspecting results, and tying things together, with a real programming language.
Hurl is my preferred way to write integration tests. HTTP clients in programming languages never feel like a natural expression of the protocol, and require too much cognitive overhead to understand what they’re doing. Hurl reads just like Curl output, there’s no translation at all. I can read a Hurl script and immediately understand what the request will be, which is valuable.
Hi, maintainer of Hurl here, don’t hesitate to ask me any questions!
Hurl is a thin Rust wrapper over libcurl which powers all Hurl HTTP exchanges. We’ve done this to benefit from curl features (rock stability, HTTP/3 etc…). We’re really focused on the CLI usage and try fo make a fast tool (for instance, with Hurl latest version, you can run test in parallel hurl --test --parallel *.hurl - it will be the default in next release). We’ve designed Hurl to be easily integrated in CI/CD pipelines. Next priority is work on IDE support (VSCode, IntelliJ) and better error report.
I’ve used it in past projects and it’s a great alternative to postman, in particular it’s way more minimalist and simpler to integrate into other tools.
While this was submitted a year ago, it didn’t seem to garner much attention. Given this community’s interest in both networking and text-based tools, I thought it was worth another mention.
Nothing beats a REPL for this type of thing.
If I’m playing around with a new web API I usually build up a little library of utility code for setting the correct headers, building URLs, creating request content, etc. Then I can play around making requests, inspecting results, and tying things together, with a real programming language.
Hurl is my preferred way to write integration tests. HTTP clients in programming languages never feel like a natural expression of the protocol, and require too much cognitive overhead to understand what they’re doing. Hurl reads just like Curl output, there’s no translation at all. I can read a Hurl script and immediately understand what the request will be, which is valuable.
Hi, maintainer of Hurl here, don’t hesitate to ask me any questions!
Hurl is a thin Rust wrapper over libcurl which powers all Hurl HTTP exchanges. We’ve done this to benefit from curl features (rock stability, HTTP/3 etc…). We’re really focused on the CLI usage and try fo make a fast tool (for instance, with Hurl latest version, you can run test in parallel
hurl --test --parallel *.hurl- it will be the default in next release). We’ve designed Hurl to be easily integrated in CI/CD pipelines. Next priority is work on IDE support (VSCode, IntelliJ) and better error report.=> GitHub