Is it possible to stub meteor methods and publications in cypress tests?

Is it possible to stub meteor methods and publications in cypress tests?

In the docs (Testing Your App | Cypress Documentation) it says:

This means that instead of resetting the database, or seeding it with the state we want, you can force the server to respond with whatever you want it to. (…) and even test all of the edge cases, without needing a server.

But I do not find more details about that. All I can find is, that when not using the virtual user in the tests to fill the database, it is possible to call API calls on the app, like so:

cy.request('POST', '/test/seed/user', { username: 'jane.lane' })
      .its('body')
      .as('currentUser')

In my opinion that is not a “stub”. It is a method to “seed” the database.

Is it possible to tell cypress to answer a meteor method in the client code like

Meteor.call('getUser', { username: 'jane.lane' }, callbackFunction);

with some data, it would give back in production?

Rekindling an old topic here!

Methods via DDP don’t make normal REST calls (which Cypress can intercept quite easily). Has anyone got any pointers on how to test methods? E.g. Which method was called how many times with what params?