Question: How do I create different success.json based on a param? about node-mock-server HOT 6 CLOSED

And as a feature request it would be cool if you could use different success files for different params.
Like success{id}.json and the you name the files success1.json, success2.json, and so on!

from node-mock-server.

@JonWallsten Currently it's just possible to use query params as ejs variables query param in ejs

I will add the dynamic path to ejs object.
The solution (with future version 0.7.2 #9) will be:

{
      "id": <%=params.id%>,
      name: "<%-faker.name.firstName();%>"
}

You question about how to change the mock response:

• Change the expected response by using the UI
  
• Use the query param _expected=error
• Use the request header _expected=error

Expected response

An automatic check for not existing dynamic path is currently not implemented #8 .

from node-mock-server.

Cool! Then I'll wait for the next release.

Ah, i see! I thought it could be done automagically! ;)
Thanks!

from node-mock-server.

{
    "id": 1,
    "campaignId": <%=id%>,
    "name": "Test"
}

I get a reference error:
"id" is not defined.
path: undefined.
Is it because I'm using /rest/test/1 instead of /rest/test/?id=1 ?

from node-mock-server.

@JonWallsten
Yes that's because you use /rest/test/1 instead of /rest/test/?id=1
0.7.2 is released - npm install [email protected]
which includes the two issues, has arisen from your questions.

• milestone 0.7.2
• issue8
• issue9

With the new release you can use this:

{
      "id": <%=params.id%>,
      name: "<%-faker.name.firstName();%>"
}

I hope it works as you had assumed.
Thanks for your feedback and questions.

from node-mock-server.

Thank you! That's awesome!

from node-mock-server.