stepci VS verb

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.

For automated testing, you should give Step CI (https://github.com/stepci/stepci) a try

Ps. I helped build it

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

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)

There’s also Step CI: https://stepci.com

Disclaimer: I’m one of the authors

It's a config driven uptime monitoring service powered by Step CI, an open source API testing framework.

You might try DiY-ing it with this open-source framework - https://stepci.com/

plz-see: Interactive HTTP client, similar to restclient and verb, but using Elisp instead of a special text-based syntax.

Ah, btw. I just realized, verb's verb-send-request-on-point doesn't always properly work with source blocks. So I pushed a fix, PR is here.

have you checked this https://github.com/federicotdn/verb . Its emacs package and i am able to write and test api's with text files.

Not as usable for testing, but verb.el[1] is a great tool for doing something very similar in org-mode

[1] https://github.com/federicotdn/verb

I've been a long time user of the org-mode code blocks feature—storing runnable code block inline in the document. Something I've recently started using is verb to include HTTP requests in my documents when I'm testing out web APIs.

Looks also interesting, but it doesn't fit my use cases: I need custom functions to grab values/data from other sources (e.g. pocket-reader.el).restclient` is more about having pre-defined HTTP requests (path, headers, payload etc.) in a buffer and a major mode for executing the requests. Pretty much the same what verb offers.

There is also verb.el.