venom
hurl
venom | hurl | |
---|---|---|
6 | 42 | |
976 | 10,994 | |
1.8% | 4.0% | |
7.3 | 9.9 | |
9 days ago | 3 days ago | |
Go | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
venom
-
Ask HN: What's your favorite software testing framework and why?
You can also load fixtures in database directly, work with Kafka queues both as a producer (e.g. write an event to a Kafka queue, wait a few seconds and see that it was consumed by the service you test, and that some side effects can be observed) or as a consumer (e.g. make sure after an HTTP call, an event was correctly pushed to a queue), or even read a mailbox in IMAP to check that your service correctly send an email.
It's a bit rough on the edges sometimes, but I'd never go back on writing integration tests directly in my programming language. Declarative is the way to go.
[1]: https://github.com/ovh/venom
-
Easy Integration Testing with Venom!
To write and run our integration tests, we'll use Venom. Venom is a tool created and made open-source by OVHcloud: https://github.com/ovh/venom
- Venom: Manage and run your integration tests with efficiency
-
Show HN: Step CI – API Testing and Monitoring Made Simple
From my experience, generated tests are worthless for anything more serious than smoke tests. I prefer working with no tests than automated tests, I feel they give you a false sense of confidence.
The Step CI engine itself looks good though. It looks like a cleaner, but less powerful version of a tool (open source, build in-house) we used when I worked at OVHcloud, Venom: https://github.com/ovh/venom
Here's an example test file for the HTTP executor of Venom: https://github.com/ovh/venom/blob/master/tests/http.yml it's very close to Step CI format.
I'd still use Venom because it's way more powerful (you have DB executors for example, so after executing a POST request you can actually check in DB that you have what you expect) and I prefer focusing on actually writing integration tests instead of generating them.
Maybe this post sounds harsh (I feel it as I write it because I have strong feelings against test generation) but I think your approach is a good one for actually writing automated tests. Testing APIs declaratively like this has a great benefit: your tests work on an interface. You can migrate your API to a whole new stack and your tests remain the same. I did it multiple time at OVHcloud: one time migrating a huge API from a Go router to another (Gin->Echo), and another time migrating public APIs from a legacy, in-house Perl engine to a Go server.
-
Debugging with GDB
I still struggle with GDB but my excuse is that I seldom use it.
When I was studying reverse engineering though, I came across a really cool kit (which I've yet to find an alternative for lldb, which would be nice given: rust)
I'd recommend checking it out, if for no other reason than it makes a lot of things really obvious (like watching what value lives in which register).
https://github.com/hugsy/gef
LLDB's closest alternative to this is called Venom, but it's not the same at all. https://github.com/ovh/venom
-
Do you write integration tests in go?
We incorporated [Venom](https://github.com/ovh/venom) into our workflow. It's great for initiating and managing a suite of yaml based tests. It didn't work out of the box for us due to the heavily asynchronous nature of our system, but after a few additions, it has helped my team greatly. We were often afraid to make large changes to critical pieces of the system since a full regression test could take a week or so to check everything. Now it takes an hour.
hurl
-
Bruno
I tried Hurl after Insomnia went the way of Postman. The highlights you list were the strong drivers for testing it out. Where Hurl fell short was composing requests. Example: X.hurl response has authToken. Y.hurl uses authToken. Z.hurl uses authToken. There's no import ability[1], so you've got to use other tooling to copy X.hurl into Y.hurl and Z.hurl.
Ultimately settled on Bruno. It's backed by readable text files[2] as well. The CLI works for scripting. And the GUI is familiar enough that I've managed to convert Postman holdouts at my dayjob.
[1]: https://github.com/Orange-OpenSource/hurl/issues/1723
[2]: https://docs.usebruno.com/bru-language-samples.html
-
Is there a good REST API development tool like Postman written in Rust?
I haven't used it myself, but maybe something like Hurl? It's not a GUI like Postman though
-
Insomnia REST client now requires an account
No, you got what's you write. If you want, you can see the run curl's command, save it in a script and replay it without Hurl. You can check the source code here [1]
[1]: https://github.com/Orange-OpenSource/hurl
-
I was wrong about Vim and Neovim
You might check out hurl for a RestAPI tool replacement. There is also a vim plugin for it, although I have not used it. Someone already mentioned dadbod (which I think works great on its own), but if you are curious there is also a plugin to add a UI on top of it.
- Hurl, run and test HTTP requests with plain text
-
Encrypted API request Docker Container?
just write a simple frontend on top of https://github.com/Orange-OpenSource/hurl
-
Hurl 4.0.0
We've a more "classic" changelog in GitHub [1], I see the blog post as an editorial view of the changelog: highlights of main features/changes with some context.
[1] https://github.com/Orange-OpenSource/hurl/releases/tag/4.0.0
-
Hurl, a terrible (but cute) idea for a language
I must say that the name is already taken by another tool language https://github.com/Orange-OpenSource/hurl which is a very good idea(similar to httpYac)
-
Hurl 3.0.0, run and test HTTP requests with plain text and curl
GitHub: https://github.com/Orange-OpenSource/hurl
-
Hoppscotch, web based Postman alternative, can now be fully self hosted
That's why we have hurl
What are some alternatives?
godog - Cucumber for golang
websocat - Command-line client for WebSockets, like netcat (or curl) for ws:// with advanced socat-like functions
dockertest - Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work.
glow - Render markdown on the CLI, with pizzazz! 💅🏻
testcontainers-go - Testcontainers for Go is a Go package that makes it simple to create and clean up container-based dependencies for automated integration/smoke tests. The clean, easy-to-use API enables developers to programmatically define containers that should be run as part of a test and clean up those resources when the test is done.
plugin-openapi - Step CI OpenAPI support
stepci - Automated API Testing and Quality Assurance
libcurl - A command line tool and library for transferring data with URL syntax, supporting DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS. libcurl offers a myriad of powerful features
gotestfmt - go test output for humans
Karate - Test Automation Made Simple
gotestfmt - go test output for humans