verb VS Karate

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.

This is why we need better tools which will give benefits for the added complexity. If you need to create both the feature files AND the code, it's just complexity with little benefits. But frameworks like https://github.com/karatelabs/karate or https://github.com/Endava/cats are hiding this complexity and remove the code layer entirely. Which, in my view, this is where you need to be in 2023, particularly for API testing.

- https://insomnia.rest/ - https://hoppscotch.io/ - https://github.com/karatelabs/karate - https://github.com/warmuuh/milkman

Congrats on the launch ! I'm the lead dev of [Karate](https://github.com/karatelabs/karate) and was wondering if you had come across it. I strongly agree that collaboration should be [via Git](https://www.karatelabs.io/first-class-citizens) and the IDE and traditional solutions fall short. I hope Karate's syntax passes your "memory friendly" test :) We get regular feedback is that it is easy to read and even non-programmers can pick it up. One thing I feel we do really well is chaining of HTTP requests. And we have plugins for [IntelliJ](https://plugins.jetbrains.com/plugin/19232-karate) and [VS Code](https://marketplace.visualstudio.com/items?itemName=karatela...).

Maintaining a tool like this as open-source is hard, all the best !

FWIW https://github.com/karatelabs/karate is 83% Java.

We use karate to test our fully integrated graphql backend. Has Gherkin language support.

Try Karate

Take a look at Karate.