Very interesting, I was hacking up Another Bash Script wrapping curl and grep earlier in a CI pipeline as a smoke test to check a docker image exposes a webserver that responds to the health check endpoint successfully (basic smoke test). It works, and requires nothing installing into the CI environment, but this looks like a good fit for that.
Could verify the root URL responds with the right Content-Type and the page contains the right phrases, as well as health endpoint being correct. I like the diff output when the body differs expectations too - replicating that would be more work than I’m willing to spend with bash/curl/grep.
Started trying to use this at $DAYJOB today, and it like it! One downside I’ve seen after using it for a few hours is that it’s a bit clunky to use for more ad-hoc testing because you can’t (afaict) hit a specific endpoint you’ve defined within your hurl file. I wound up falling back on my usual combo of Postman/IntelliJ HTTP client for that part of my workflow. It does seem like it’s still useful for more structured testing though!