41–50 of 104 posts
Feedback: The homepage ( https://hurl.dev/ ) doesn't really make it clear - is this an interactive tool or not? If I understand it correctly, you're supposed to save that example as a file and run 'hurl example.hurl'. It would make it easier to understand if that sample code box had a headline saying e.g. [example.hurl].
Are there use cases beyond testing that anyone here has actually done?
Anyway, for me, hurl looks like an evolution of curl...which makes sense since its built off of curl (https://hurl.dev/#powered-by-curl). So, for uses-cases that might reach beyond curl, that's when i might reach for hurl as well. No doubt, there could be other use-cases for hurl.
I see some parallels to Hurl, but having everything inside Emacs is hard to beat, just thinking about using M-x jq-interactivly for json responses ...
Please make this the industry standard for testing APIs. I'm tired of having to look at Postman screenshots sent from QA. I'm tired of having to wait for them to press Send once I've implemented a fix. I know they're tired of waiting for me to do that, too. Hurl is something both the devs and QA can speak and write. It can be automated and a part of CI. It makes communicating expectations straightforward. It can be c…
I personally like the approach of defining things via an OpenAPI and then using Dredd to validate the spec against itself. Even for tools that generate the spec from source code, it is usually still possible for user error to define the metadata for an endpoint incorrectly. Dredd catches that.
Please make this the industry standard for testing APIs. I'm tired of having to look at Postman screenshots sent from QA. I'm tired of having to wait for them to press Send once I've implemented a fix. I know they're tired of waiting for me to do that, too. Hurl is something both the devs and QA can speak and write. It can be automated and a part of CI. It makes communicating expectations straightforward. It can be c…
This is one of the best examples of a modern Unix program I have seen: - It accepts input on stdin - It sends output to stdout - Does not appear to be littered with unicode emoji everywhere - It comes with man pages (and pretty good ones too!) - The hurl file extension is four characters long instead of three, thank goodness we're finally past MS-DOS compatibility concerns! This looks like something I might take seri…
and VMS!
We at Adaptive[1] extensively use hurl.dev to automate our testing. All our internal product flows are tested via hurl. It is the best thing that we have ever implemented in our org to stabilize the product. Everytime before we deploy, we run bunch of automated tests written in hurl, for onboarding, signups, critical flows etc. That are containerized and can run in parallel. We have been building internal tools aroun…
Please make this the industry standard for testing APIs. I'm tired of having to look at Postman screenshots sent from QA. I'm tired of having to wait for them to press Send once I've implemented a fix. I know they're tired of waiting for me to do that, too. Hurl is something both the devs and QA can speak and write. It can be automated and a part of CI. It makes communicating expectations straightforward. It can be c…
The bigger problem here is that you have QA, not the lack of tooling.
if you don't have devs there are no bugs, problem solved.
Earlier quoted context omitted.
The bigger problem here is that you have QA, not the lack of tooling.
The bigger problem here is that you have devs, devs make bugs. if you don't have devs there are no bugs, problem solved.