fix: vue2 global directives in component testing

[crazyk2]

User facing changelog

mount() now accept a extensions.directives option, which will be registered globally for Vue2 component testing

Additional details

To register custom vue directive you should pass option like

    mount(HelloWorld, {
      directives: { customDirective: { /* stub */ }}
    })

and this works but only for first level mounted component.

If you test component with nested components which have custom directive, you see error in console
[Vue warn]: Failed to resolve directive: customDirective

Steps to test

How has the user experience changed?

Now you can pass

  mount(HelloWorld, {
    extensions: {
      directives: { customDirective: { /* stub */ }}
    },
  })

And it will be registered globally and works everywhere.

See example /system-tests/projects/vueclivue2-configured/src/components/HelloWorld.cy.js

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[CLAassistant]

All committers have signed the CLA.

[lmiller1990]

Looks good... I guess this is a bug in Test Utils, I wonder if we should patch it there, too. Happy to do it here, though - thanks for the PR and test.

[lmiller1990]

Nice job figuring out where to add a test 👍

[lmiller1990]

Hmmm looks like some CI failures. I will take a look.

[lmiller1990]

I pushed a commit to fix the tests.

[cypress-bot]

Released in 11.1.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v11.1.0, please open a new issue.