cy.intercept not matching a specific GraphQL mutation

Question

I have 8 GraphQL calls hitting /graphql. cy.intercept('POST','/graphql') catches all of them but I only want to stub the CreateOrder mutation. Matching by req.body.operationName does not seem reliable. What is the current best practice?

Arjun Patel · Accepted Answer

Match on the request body inside cy.intercept using a function. Do NOT rely on url-only matching for GraphQL. This lets you stub exactly the CreateOrder mutation and leave the rest untouched.

cy.intercept('POST', '/graphql', (req) => {
  if (req.body?.operationName === 'CreateOrder') {
    req.alias = 'createOrder';
    req.reply({
      data: { createOrder: { id: 'ord_123', status: 'PENDING' } }
    });
  }
});

cy.get('[data-cy=checkout]').click();
cy.wait('@createOrder').its('request.body.variables.total').should('eq', 4999);

Carlos Mendes · Answer

One more nice pattern: keep the matcher in a helper so multiple specs can stub the same mutation without duplicating body inspection code.

export const stubGraphql = (op, response) => {
  cy.intercept('POST', '/graphql', (req) => {
    if (req.body?.operationName === op) req.reply({ data: response });
  }).as(op);
};

cy.intercept not matching a specific GraphQL mutation

2 answers