returning a promise in a custom command should throw

You cannot return a 3rd party promise from a custom command because this breaks the chaining between cypress commands. This is because the .then methods are not the same.

It is an anti-pattern anyway because all cypress commands are promises.

For instance doing this:

Cypress.addParentCommand('login', function (email, password) {
  return new Cypress.Promise((resolve) => {
    cy.request({
      method: 'POST',
      url: '/login',
      body: {email, password}
    })
    .then(result => {
      resolve(result.body);
    })
  })
})

…can simply be rewritten as:

Cypress.addParentCommand('login', function (email, password) {
  cy.request({
    method: 'POST',
    url: '/login',
    body: {email, password}
  })
  .its("body")
})

[brian-mann]

Browsers have no notion of require. Browsers must have a build process to parse the dependency tree and generate JS files. Cypress does this with browserify or you can swap this out with webpack.

You cannot import Meteor that way because it would create a whole new instance which has nothing to do with the Meteor instance your app is using.

In order to access the Meteor in your application is the same way you’d access it from the dev tools - you just set it on window and then access it with cy.window().then((win) => win.Meteor )

[jennifer-shehane]

@panneerselvamc Can you include the test code you’ve written where you call the function?