In our last post, we showed that there is an easy way to generate automated tests for Rest APIs from your specification.<p>Since the last release, we have added some new features:<p><pre><code> - Generate tests from your API spec in the CLI
- Run tests against gRPC APIs automatically
- Get request and response information when your tests fail
- Generate fake data and use it in the requests
- Bring your own test data (from .csv)
- More intuitive CLI interface
</code></pre>
We built this because we wanted a simple, developer-friendly way to automate API testing without relying on cloud solutions. You can integrate it with Docker, GitHub Actions and Node. Your tests can have multiple steps, with shared context between them. Lastly, you can use it as a library and in combination with other testing tools like Jest, Ava, Mocha (and soon Insomnia).<p>If you want to step out of locked-in cloud solutions, give our tool a try.
Just wanted to hop in here as founder of Checkly that I think this is awesome. Coded API checks, or checks living in your codebase make total sense. I'm also kinda humbled as I launched Checkly as an indie hacker couple years back and later went VC route. Being mentioned by name by an alternative is kinda really cool! Good luck StepCI team and let's make the web (and the APIs) more reliable!
I really like the captures features.<p>It lets you follow a semantic API path through multiple API calls.<p><a href="https://github.com/stepci/stepci/blob/main/examples/captures.yml" rel="nofollow">https://github.com/stepci/stepci/blob/main/examples/captures...</a>
This looks pretty nice! I had to do a bunch of mocking and magic to mock servers and clients for testing gRPC endpoints, and I think something like this would make it a lot simpler.
Congrats on the launch. I'm excited to try this out.<p>Some questions:<p>1. Is it possible to include headers at the workflow-level. I can't determine whether this is possible from reading the docs. Use case: include Authorization header for all tests/steps<p>2. Is it possible to run some command or query before a workflow/test/step. Use case: obtaining auth tokens
This looks really interesting! As a senior software engineer it looks much cleaner and simple than what I worked with, PMed you on LinkedIn with some questions :)