Problem with multiple mocks in the same story.

[NicolasBonduel]

I am trying to mock multiple requests for the same component, such as:

Appointment.parameters = {
  mockData: [
    {
        url: `${process.env.ENDPOINT}/appointments/CURRENT`,
        response: responses.CURRENT,
    },
    {
        url: `${process.env.ENDPOINT}/appointments/EARLY`,
        response: responses.EARLY,
    },
    {
        url: `${process.env.ENDPOINT}/appointments/LATE`,
        response: responses.LATE,
    },
    {
        url: `${process.env.ENDPOINT}/appointments/CANCELLED`,
        response: responses.CANCELLED,
    },
  ],
};

It seems that only the latest mockData of the array is used, and the other ones are ignored. Am I doing something wrong?

[adamgilmour]

Yep, I'm experiencing the same issue

[NicolasBonduel]

I found the issue and fixed it in the PR above.

An easy way to fix it in the meantime is to set the method in each mockData. On my example, it would be:

Appointment.parameters = {
  mockData: [
    {
        url: `${process.env.ENDPOINT}/appointments/CURRENT`,
        response: responses.CURRENT,
        method: 'GET',
    },
    {
        url: `${process.env.ENDPOINT}/appointments/EARLY`,
        response: responses.EARLY,
        method: 'GET',
    },
    {
        url: `${process.env.ENDPOINT}/appointments/LATE`,
        response: responses.LATE,
        method: 'GET',
    },
    {
        url: `${process.env.ENDPOINT}/appointments/CANCELLED`,
        response: responses.CANCELLED,
        method: 'GET',
    },
  ],
};

@adamgilmour, this might be interesting for you.

[nutboltu]

@NicolasBonduel the change reflects on version 1.7.0