test: adds weekly scheduled smoke tests

[AriPerkkio]

This PR fixes/implements the following bugs/features

• Bug
• Feature
• Breaking changes
• Test improvements

What

Adds weekly scheduled smoke tests to be run on every Sunday at 00:00. Tests can also be trigger manually (workflow_dispatch). These tests will be looking for rule crashes.

Some example ESLint community plugins that are using this tool already:

• eslint-plugin-react
• eslint-plugin-jest
• eslint-plugin-jest-extended
• eslint-plugin-jest-dom
• eslint-plugin-testing-library
• eslint-plugin-unicorn

Helps finding issues like below even before releasing:

• Cannot read property 'name' of undefined #27
• Crash in no-conditional-tests when using array destructuring #21
• Crash in expect-expect rule when calling function without assignment #20

Here is the first run: AriPerkkio#1

Detected 26770 ESLint reports and/or crashes.
Scanned 5288 repositories.

Rules:

• vitest/expect-expect
• vitest/no-conditional-tests
• vitest/lower-case-title

How

Plugin maintainer making sure all existing rules do not crash

Utilizes https://github.com/marketplace/actions/eslint-remote-tester-runner. Each test run will check as many repositories as it can in 5 hours 30 minutes (default value of timeLimit). Utilizes over 10K repositories from eslint-remote-tester-repositories.

Available configuration options:

• eslint-remote-tester-run-action: https://github.com/marketplace/actions/eslint-remote-tester-runner#action-parameters
• eslint-remote-tester: https://github.com/AriPerkkio/eslint-remote-tester#configuration-options

When test fails the @github-actions bot will open new issue with title Results of weekly scheduled smoke test. It will reuse the existing issue if previous one hasn't yet been closed. It's recommended to close the issues once their findings are fixed.

Below are two examples of test results:

• Results of weekly scheduled smoke test jsx-eslint/eslint-plugin-react#3328
• Results of weekly scheduled smoke test jsx-eslint/eslint-plugin-react#3376

[veritem]

Thank you!

[AriPerkkio]

@veritem the ts-node is actually required, it was now removed by 978dad5.

https://github.com/AriPerkkio/eslint-remote-tester#eslint-remote-testerconfigjs

Configuration file can also be written in TypeScript if ts-node is installed.

[veritem]

I haven't read about that, let me add it in another commit.