ci: add test project

[MikeMcC399]

Situation

Currently CI tests running in the circle.yml pipeline provide the following coverage:

Command	Coverage
npm run eslint	lints the plugins' source code
npm test	uses Jest to run the ESLint Rule Tester against current rules
npm run test:legacy	uses Jest and the end-of-life ESLint v8 Rule Tester against legacy rules

Tests showing eslint-plugin-cypress running in typical end-user configurations are missing. This represents a test coverage gap.

If there are any problems with the package definition and content provided by package.json or with the examples in the README document this would not be picked up by the current tests.

Change

1. Add a Cypress test-project configured with the default set of full scaffolded Cypress tests.
2. Add jobs and workflows to:
   • build a package tarball corresponding to the published package on the npm registry
   • test different typical ESLint configuration files against the scaffolded tests

Non-goal

End-user testing of legacy (deprecated non-flat) configurations.

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

[MikeMcC399]

https://app.circleci.com/pipelines/github/cypress-io/eslint-plugin-cypress/422/workflows/91b20578-9ce3-47ee-83b8-a34f5620b806

[jennifer-shehane]

There tends to be issues sometimes hitting the https://jsonplaceholder.cypress.io URL, because of how we rate limit those requests. Not a blocker, just bringing it up if that ends up becoming a pattern to watch for.

[MikeMcC399]

@jennifer-shehane

Thanks for updating the "Cypress App" term!

There tends to be issues sometimes hitting the https://jsonplaceholder.cypress.io URL, because of how we rate limit those requests. Not a blocker, just bringing it up if that ends up becoming a pattern to watch for.

Actually this will not be a possible pattern here because CircleCI doesn't run Cypress. It only runs ESLint against the Cypress scaffolded project code. Cypress is only used in development to scaffold the project, then it is uninstalled. In CircleCI Cypress is not installed at all.

There are instructions in the README for running Cypress locally and that is the only situation where https://jsonplaceholder.cypress.io would come into play.

So I think we're good. 🙂

[jennifer-shehane]

🎉 This PR is included in version 4.2.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀