test: protect yarn modern pnp example against cypress script redefinition

[MikeMcC399]

For the Yarn Modern Plug'n'Plug example this PR changes the command used to run Cypress from

• command: yarn cypress run

to

• command: yarn run --binaries-only cypress run

This makes sure that the Cypress binary is called instead of a possible user-defined script with the name of cypress.

This follows on from issue #941 where it emerged that users had been defining such a script name which effectively overwrites the cypress name. When there is a script and a binary with the same name yarn run (Yarn Classic and Modern) selects the script. Yarn Modern offers the --binaries-only option to make the choice deterministic. Yarn Classic does not offer this option.

Verification

Run the following local and GitHub tests.

Run them again after temporarily adding a script to examples/yarn-modern-pnp/package.json where cypress is defined as cypress open :

  "scripts": {
    "cypress": "cypress open",
    "test": "cypress run"
  },

Local test

cd examples/yarn-modern-pnp
yarn
yarn run --binaries-only cypress run

Confirm that Cypress runs in headless mode and that the Cypress app does not open.

GitHub test

Manually run .github/workflows/example-yarn-modern-pnp.yml with the above cypress script defined.

Confirm that the workflow runs to completion in headless mode and does not hang up.

Reference

• Yarn Modern CLI yarn run

[cypress-app-bot]

• 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.

[github-actions]

🎉 This PR is included in version 5.8.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀