test: add smoke tests

[AriPerkkio]

Checks

• I have read the contributing guidelines.
• If some rule is added/updated/removed, I've regenerated the rules list.
• If some rule meta info is changed, I've regenerated the plugin shared configs.

Changes

• Adds smoke tests to the project
• Adds two new development dependencies
• Adds one new Github Action

Github Action will be run once a week by a schedule. It can also be triggered manually. In addition it is also run after each release as requested in #341 (comment).

When eslint-remote-tester finds errors it will create an issue in this project. Here are some example reports: https://github.com/yannickcr/eslint-plugin-react/issues?q=author%3Aapp%2Fgithub-actions.

Context

Closes #341.

• Use case description: https://github.com/AriPerkkio/eslint-remote-tester#plugin-maintainer-making-sure-all-existing-rules-do-not-crash
• Used Github Action: https://github.com/AriPerkkio/eslint-remote-tester-run-action
• Example run: https://github.com/AriPerkkio/eslint-plugin-testing-library/actions/runs/1517040258

[Belco90]

Thanks @AriPerkkio! We finally moved the smoke tests here. It seems there is some regexp issue to fix in #509 but should be an easy one.

[Belco90]

@all-contributors please add @AriPerkkio for test

[allcontributors]

@Belco90

I've put up a pull request to add @AriPerkkio! 🎉

[github-actions]

🎉 This PR is included in version 5.0.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀