Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP support #64

Open
meiremans opened this issue Aug 30, 2020 · 2 comments
Open

HTTP support #64

meiremans opened this issue Aug 30, 2020 · 2 comments

Comments

@meiremans
Copy link
Contributor

meiremans commented Aug 30, 2020

I'm currently writing a workaround to be able to do an HTTP request, with the test JSON in the body piping it to a file, run curl runnings and then piping the output back to the result of the call.

This way curl runnings could integrate with my front end to select test cases.

Would it be possible to support this natively?

in case you are interested, I just wrote a small node wrapper around it. You can find it here:

https://github.com/meiremans/curl-runnings-http

@aviaviavi
Copy link
Owner

Interesting! It certainly could be done. On the other hand now that you've made a separate repo, keeping that separated might actually be the better way to go. The concerns of running curl-runnings itself and this is web service are nicely decoupled here, so I might lean towards keeping it way. Open to suggestions though!

Now that you've written curl-runnings-http, do you think it would be advantageous to merge them / add this server functionality? What are those advantages?

@meiremans
Copy link
Contributor Author

The disadvantage -for now- is that i just write the input to json file, start curl runnings, write to output file and then read that file.

So it's not multi threaded, only 1 test can be run at the same time. but so is the original curl runnings.

Anyway I proposed the functionality because I needed it and it didn't exist. If somebody else needs it too a, he has to go through the hassle of installing docker or nodejs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants