Hi!
I created this new desktop app (made with Electron) to easily mock REST APIs locally. It's available for Windows / Linux / OSX and still in beta but with lots of features and a lot more to come.
I developed it for my colleagues and me to help us easier the process of working on upcoming APIs still under development.
Feel free to give it a try, any feedback is welcome :) Thanks!
To answer a common question: what differentiate Mockoon from Postman mocking option? It's easier to set up, 100% local (no remote deployment), and requires no account.
Hi! I have been looking for something, its awesome!
Apart the main use-case, I'm also trying to figure out how to fit it for this use-case – For a specific URL I would like to capture all requests made from the frontend app (JS) in production to the backend, and then replay it for a local version of the frontend.
This project is really cool for me. Here's my personal use case that it would solve.
I always begin every Node/Express server project with a unit and integration test file using the request-sync library to make a sequence of synchronous requests and assert everything about each request in each step before continuing. But I can never run those scripts to completion until my server is written, which is much more difficult to test than my test script. (Yes, I'm looking for a meta-test of my test script.) Questions like "am I checking the data in the correct way" and "are all my status code checks the correct number" would be answered if I could make a fake server first, then a unit test, then the real server.
It's easier to make example data than to write a script to check everything in generality if I don't know exactly how the server should behave.
Thank you!
I have a use case at work where I work exclusively on a frontend application. And sometimes I need to mock new API routes not developed yet by the backend team. I could hardcode some things directly in the application but mocking with an external tool is more convenient.
Branding suggestion: I would change the name/logo. Not to be PC, but because the name/logo gave me an immediate cringe and I would have a hard time telling my friends about this service by name. I know it's unintentional by you. Please take a look at the 2nd definition: http://www.dictionary.com/browse/coon
Omg! English is not my main language and I did not know about this second meaning :(
This reminds me that most of the time when I try to find a name for something I go to urban dictionary, just in case :D I forgot to check this time...
Anyway, I do not plan to change the name for now. If it becomes obvious that it is offensive for some I will definitely consider this.
Raccoon and "coon" are uh extremely different things. This is obviously evoking the animal and not the racial epithet. The problem is not that raccoons exist, the problem is that humans were likened to wild animals. No humans are depicted here as animals. There is nothing wrong with raccoons.
[+] [-] 255kb|8 years ago|reply
To answer a common question: what differentiate Mockoon from Postman mocking option? It's easier to set up, 100% local (no remote deployment), and requires no account.
[+] [-] vorotato|8 years ago|reply
[+] [-] RubenSandwich|8 years ago|reply
[+] [-] 255kb|8 years ago|reply
[+] [-] ko5ta|8 years ago|reply
Exporting to flat-file would allow mock environments to be versioned using a VCS.
Importing OpenAPI spec (swagger) files could simplify initial setup.
[+] [-] 255kb|8 years ago|reply
[+] [-] ReedJessen|8 years ago|reply
Also, exporting swagger as well as importing swagger may allow automating new version deployments on AWS API Gateway and the like.
[+] [-] tenaciousDaniel|8 years ago|reply
[+] [-] 255kb|8 years ago|reply
[+] [-] zakshay|8 years ago|reply
Apart the main use-case, I'm also trying to figure out how to fit it for this use-case – For a specific URL I would like to capture all requests made from the frontend app (JS) in production to the backend, and then replay it for a local version of the frontend.
[+] [-] ReedJessen|8 years ago|reply
[+] [-] endroits1|8 years ago|reply
[+] [-] vortico|8 years ago|reply
I always begin every Node/Express server project with a unit and integration test file using the request-sync library to make a sequence of synchronous requests and assert everything about each request in each step before continuing. But I can never run those scripts to completion until my server is written, which is much more difficult to test than my test script. (Yes, I'm looking for a meta-test of my test script.) Questions like "am I checking the data in the correct way" and "are all my status code checks the correct number" would be answered if I could make a fake server first, then a unit test, then the real server.
It's easier to make example data than to write a script to check everything in generality if I don't know exactly how the server should behave.
[+] [-] 255kb|8 years ago|reply
[+] [-] notimewaste|8 years ago|reply
[+] [-] TheBiv|8 years ago|reply
[+] [-] watty|8 years ago|reply
I think it's a stretch. If the word is that taboo to you then what do you call those striped tail critters who get in the garbage? Rac--n?
[+] [-] jessemillar|8 years ago|reply
[+] [-] danielvaughn|8 years ago|reply
[+] [-] 255kb|8 years ago|reply
Anyway, I do not plan to change the name for now. If it becomes obvious that it is offensive for some I will definitely consider this.
[+] [-] vorotato|8 years ago|reply
[+] [-] vortico|8 years ago|reply
[+] [-] quickthrower2|8 years ago|reply
https://en.m.wikipedia.org/wiki/Coon_cheese