Config routes with no response fail to be recognised as a route

Current behavior:

If we try to create the following route:

cy.route({
  method: 'GET',
  url: '**/some-route',
  status: 400,
}).as('someRoute');

This is failed to be picked up by Cypress as a valid route:

cy.wait('@someRoute'); // The route is not recognised, so this assertion will fail

The current workaround for this is to provide an empty response object, which is technically not correct behaviour, as this particular route does not return any response (not even an empty JSON payload):

cy.route({
  method: 'GET',
  url: '**/some-route',
  status: 400,
 response: {}
}).as('someRoute');

Desired behavior:

Routes without responses should be able to be configured / considered as valid routes by Cypress:

cy.route({
  method: 'GET',
  url: '**/some-route',
  status: 400,
}).as('someRoute');

Steps to reproduce: (app code and test code)

Same as per the current behaviour

Versions

Cypress: Latest, 3.2.0 Operating System: macOS High Sierra 10.13.6 Browser: Chrome and/or Electron 59

[jeep87c]

I’m having the exact same issue. It also fails doing something like cy.route('/some/route')

[emilyrohrbough]

In the upcoming v12.0.0 release, the deprecated cy.route() and cy.server() commands and the deprecated Cypress.Server.defaults API will be removed. This has been replaced with cy.intercept(). Close as this is no longer application.

Please try recreating this issue with the latest Cypress version and cy.intercept(). If you are still having problems please open a new Github issue.