The abstraction is provide better UX. Anyone will have to write stuff over telnet to provide chained requests, variables, assertions, etc. Once you do that, you basically get a reimplementation of hurl.
Curl is a good tool to familiarize yourself with, but I've written test with curl and bash it is very cumbersome this is another level of awesomeness for that. If all you are going to do is connect to a server with some json, then curl is ok, I agree that nc/telnet/socat might be a bit extreme.
Hurl is not enough for some of the tests I want to write, i.e. testing sending a 50MB file, or dynamic content.
toastercat|3 years ago
emj|3 years ago
Hurl is not enough for some of the tests I want to write, i.e. testing sending a 50MB file, or dynamic content.
zodvik|3 years ago
If you're going to do a single request or a few requests in isolation, curl is the way to do.
If you wanna do a full fledged testing suite, might as well using a proper scripting language or a test framework.
Hurl hits the spot between those two for me.