3.11 -> 3.12 regression in URL overrides

[vroegop]

In version 3.11 I have everything set up to run multiple endpoints with different responses. In 3.12 however, they suddenly respond with the same value instead of different values.

As you can see, the following 2 mocks have a different URL. They should return their own response based on the request URL.

{
  "name": "getGebruikerRollen",
  "request": {
    "url": "/api_v2/gebruikers/mijnGebruiker/rollen",
    "method": "GET"
  },
  "responses": {
    // ... RESPONSES 1
  }
}

{
  "name": "getMijnGebruiker",
  "request": {
    "url": "/api_v2/gebruikers/mijnGebruiker",
    "method": "GET"
  },
  "responses": {
    // ... RESPONSES 2
  }
}

In 3.11 I get the correct responses. In 3.12 I always get the response from the /api_v2/gebruikers/mijnGebruiker even on the /api_v2/gebruikers/mijnGebruiker/rollen call.

[jboon]

I can confirm this issue. Version 3.11.2 works as expected. Regression is introduced in version 3.12

{
  "name": "recipes",
  "request": {
    "url": "recipes",
    "method": "GET"
  },

{
  "name": "recipes-6-tasks",
  "request": {
    "url": "recipes/6/tasks",
    "method": "GET"
  },

Request with url recipes/6/tasks returns the response from the mock with "name"="recipes".

I'm running on node v20.14.0

[mdasberg]

@vroegop @jboon, checking.

[mdasberg]

Hi @vroegop @jboon,

I was able to reproduce this with the following 2 mock files

I tried it with the following mocks.

{
  "name": "recipes",
  "request": {
    "url": "recipes",
    "method": "GET"
  },
  "responses": {
    "ok": {
      "data": {
        "result": "recipes"
      },
      "default": true
    }
  }
}

and

{
  "name": "recipes-6-tasks",
  "request": {
    "url": "recipes/6/tasks",
    "method": "GET"
  },
  "responses": {
    "ok": {
      "status": 200,
      "data": {
        "result": "recipe-6-tasks"
      },
      "default": true
    }
  }
}

The problem is that the file that is loaded first will be returned first because both /recipes and /recipes/6/tasks match when hitting /recipes/6/tasks.

There is a solution to this issue, which is to use a regex, to make this work you can do the following

{
  "name": "recipes",
  "request": {
    "url": "recipes$",
    "method": "GET"
  },
  "responses": {
    "ok": {
      "data": {
        "result": "recipes"
      },
      "default": true
    }
  }
}

Can you let me know if this works for you?

[lord-carlos]

Can confirm the bug, and can confirm @mdasberg work around works.
I don't want to go through all my files to see where I have problematic URLs, so I might downgrade. I hope the next version fixes this.

[Zialus]

Hi @mdasberg, can you just confirm if the new behaviour is the expected behaviour?

[mdasberg]

Hi @Zialus,

This has been introduced by the upgrade of the dependency glob.
The order is different between v8.* and v10.*

You can solve this in 2 ways:

1. use regex to make the mocks unique (see above)
2. use a naming convention making the least specific with the lowest number:

ie:

1.recipies.mock.json -> "url": "recipes"
2.recipies.mock.json -> "url": "recipes/6/tasks"

I would advice to go for option one to make the mocks more specific.