Show HN: New way to test APIs with OpenAPI and Postman

My problem with Postman is that is very expensive for what it provides. It is $12 per user per month. Microsoft 365 Personal that comes with 1T of storage and all the standard office applications costs $7, business plan starts from $5 to $12 (If only MS Teams was a little better product...).<p>IntelliJ costs $150 per year and it gives way more value than some tool that can just run tests and allow to share them between people.<p>Postman has some convenience to run quickly REST call, right, but for anything more serious it is more productive to use Robotframework or after a bit of writing glue code in Java JUnit + Restassured. Everything is in the code, easily versioned.<p>I don&#x27;t know how to achieve in Postman tests versioning (different version of a test for a product version or different tests for new API version), probably this can be somehow simulated with environments, etc. but for me this is hacky and hard to maintain. I guess people just copy-paste a collection for new version.

I&#x27;ve started using Restclient, a VS Code plugin [1]. It allows me to easily add test scripts&#x2F;requests to my normal GitHub workflow and share them with team mates.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;Huachao&#x2F;vscode-restclient" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Huachao&#x2F;vscode-restclient</a>

Very cool! We use Postman collections extensively to internally document our APIs and make handoff between frontend and backend easier. We&#x27;re waffling a bit on backend schema (currently using Yup &amp; Typescript to export request&#x2F;response types, but no formal definition), but seeing this makes me think it might be worth investing in a migration to OpenAPI, just to ease documentation.

This seems really cool, but I&#x27;m curious about the ethics of creating a tool that seems to replace Postman&#x27;s paid offerings while leveraging all the free features of Postman.<p>I&#x27;m new to software development though, and I don&#x27;t have an exact understanding of how open and sharing things are, and while I do understand we are all standing on the shoulders if giants, I wonder how far that goes.<p>Maybe I&#x27;m misunderstanding though, but this seems to be solving a lot of the collaboration issues that exist on the free tier, that they sell for Enterprise postman.<p>But once again, I&#x27;m new to the culture.

I&#x27;ve been very interested in using containers to have reproducable test environments in the past. I&#x27;ve built something for this: <a href="https:&#x2F;&#x2F;bunt.build" rel="nofollow">https:&#x2F;&#x2F;bunt.build</a><p>I am interested in seeing the configuration leveraging happening in your project though. Very cool.

We have fully generated open API for our backend and public API. I&#x27;ve used cypress to test API endpoints but this requires manual setup and lots of work to collect examples.<p>I look forward to checking this out. We had a breakage in our public API this week because we didn&#x27;t have full test coverage.

Read the full blog post at <a href="https:&#x2F;&#x2F;blog.apideck.com&#x2F;announcing-portman" rel="nofollow">https:&#x2F;&#x2F;blog.apideck.com&#x2F;announcing-portman</a>

A great solution. Personally, I really liked this solution. It seems to me that this is the best thing that I have met of this kind.

I&#x27;m confused because Postman already generates a collection from an OpenAPI document. Does this do it differently somehow?

curl