I have never wanted to hurl more than I do now. But in a good way. :-)
Hurl 4.0.0
61–70 of 104 posts
Re: Hurl 4.0.0
#62Re: Hurl 4.0.0
#63Earlier quoted context omitted.
Honestly that sounds like making pilots build aircraft engines. these are different disciplines that deserve to be done well. Maybe I am biased because I spent the last 10 years in gamedev, or maybe this is another push to make devs do basically everything tech related: but if a developer tells me a feature is done I always look to QA for a nod. That nod rarely comes, the feature is not done, the developer merely got…
Then your developer should learn that "done" means more than "works on their machine". The difference between devs and dedicated QA people is that devs know the dark corners of the implementation. They know the edge cases and scenarios that they struggled with getting right. That's where most testing focus has to be. QA doesn't know any of that. They can play through some scenarios that are the expected ones from the…
Re: Hurl 4.0.0
#64Earlier quoted context omitted.
The bigger problem here is that you have devs, devs make bugs. if you don't have devs there are no bugs, problem solved.
If devs have to do QA themselves, many issues magically disappear.
it's the same with good security folk. sure you can pretend you'll catch 100% of issues, but it's a delusion, good security or quality testing is a totally different mode of thought
Re: Hurl 4.0.0
#65I really like httpyac for this purpose: https://httpyac.github.io Pretty similar with JS scripting capabilities. Has great VS Code integration in addition to its CLI.
Re: Hurl 4.0.0
#66Please 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…
There’s also Step CI: https://stepci.com (I’m one of the authors) Hurl is brilliant though
Re: Hurl 4.0.0
#67Please 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…
It allows you to write load/performance tests in JS, commit them to your repo, easily automate them in CI, send metrics to several backends, use protocols besides HTTP, with a modern CLI, and many more features.
There's also a Postman-to-k6 converter[1]. The conversion might not be perfect, but it will give you a head start.
Note that the k6 philosophy is for developers to write these tests, similarly to how you write unit/integration tests, and to break the classic QA-dev cycle.
I don't want to steal Hurl's thunder, it does look great, but it's limited in features compared to existing peformance testing tools, and I'd personally rather write tests in a programming language, than in a bespoke text format.
Re: Hurl 4.0.0
#68I've been following hurl for sometime. Where it shines from others is that it has its own DSL For testing. It is not only to make http request, but to assert response and capture data. Having said that, and hoping the maintainer is reading this: please please make it such that assertion can passed to an external script. Why am I asking this? Because, an example, you cannot still assert that a property in a collection…
The DSL would slowly creep to a Turing complete general purpose language so I agree that invoking external scripts seems reasonable. The could be quite a can of worms though because it makes the files less hermetic
what if the script was inline in the DSL? e.g. some syntax for opening a script “block”, with an annotation of the command to exec or pipe the script into
Re: Hurl 4.0.0
#69Re: Hurl 4.0.0
#70Earlier quoted context omitted.
Then your developer should learn that "done" means more than "works on their machine". The difference between devs and dedicated QA people is that devs know the dark corners of the implementation. They know the edge cases and scenarios that they struggled with getting right. That's where most testing focus has to be. QA doesn't know any of that. They can play through some scenarios that are the expected ones from the…
How big is your company and product?