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.
Exporting to flat-file would allow mock environments to be versioned using a VCS.
Importing OpenAPI spec (swagger) files could simplify initial setup.
Also, exporting swagger as well as importing swagger may allow automating new version deployments on AWS API Gateway and the like.
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.
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.
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?
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.