stepci
venom
stepci | venom | |
---|---|---|
46 | 6 | |
1,503 | 976 | |
1.9% | 1.8% | |
7.7 | 7.3 | |
about 7 hours ago | 9 days ago | |
TypeScript | Go | |
Mozilla Public 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.
stepci
- Step CI – open-source API test automation framework
- Bruno
-
Ask HN: Who wants to be hired? (December 2023)
Location: EU, Germany
Remote: Yes
Willing to relocate: Yes
Technologies: HTML, CSS, TailwindCSS, JavaScript, TypeScript, Node.js, React/Next.js, Vue/Nuxt, GraphQL, REST, Postgres, Git, AWS, Docker + K8s
GitHub: https://github.com/mishushakov
LinkedIn: https://linkedin.com/in/mishushakov
Email: hey at mish.co
Most recently, I worked at Step CI a Technical Founder and authored the API-Testing Framework (https://stepci.com) and Garph (https://garph.dev), a full-stack API-Framework, which brings the developer-experience of tRPC to GraphQL.
My passion is in making tools developers love using and make them more productive.
-
Insomnia REST client now requires an account
For automated testing, you should give Step CI (https://github.com/stepci/stepci) a try
Ps. I helped build it
-
TypeScript NPM Packages Done Right
The problem is that you can import commonjs modules in ESM but not the other way around. For stepci (https://stepci.com) we have chosen to not support ESM for this very reason. We want that the library “just works” for all our users
- Beyond OpenAPI
-
Show HN: Open-source Postman alternative with type safety
Hopscotch is not a Postman fork as far as I know.
You can also do request chaining with Step CI (https://stepci.com) and Hurl (https://hurl.dev)
-
Hurl 4.0.0
There’s also Step CI: https://stepci.com
Disclaimer: I’m one of the authors
-
I'm building an uptime monitoring service for API workflows! Looking for some fedback.
It's a config driven uptime monitoring service powered by Step CI, an open source API testing framework.
-
What are my options for cheap multi-step API testing? Datadog is ridiculous.
You might try DiY-ing it with this open-source framework - https://stepci.com/
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.
What are some alternatives?
Restfox - Offline-First Minimalistic HTTP & Socket Testing Client for the Web & Desktop
godog - Cucumber for golang
hurl - Hurl, run and test HTTP requests with plain text.
dockertest - Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work.
metlo - Metlo is an open-source API security platform.
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.
milkman - An Extensible Request/Response Workbench
gotestfmt - go test output for humans
vscode-restclient - REST Client Extension for Visual Studio Code
gotestfmt - go test output for humans
Kreya - Kreya is a GUI client for REST and gRPC with innovative features for environments, authorizations and more.
go-txdb - Immutable transaction isolated sql driver for golang