Test output even if errors is just a number

[ForbesLindesay]

If the errors field is just a number, then ESLint is currently ignoring the output field. This makes it easy to accidentally not test the output of a rule's auto-fix.

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

[mention-bot]

@ForbesLindesay, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nzakas, @mysticatea and @platinumazure to be potential reviewers.

[eslintbot]

Thanks for the pull request, @ForbesLindesay! I took a look to make sure it's ready for merging and found some changes are needed:

• The commit summary needs to begin with a tag (such as Fix: or Update:). Please check out our guide for how to properly format your commit summary and update it on this pull request.

Can you please update the pull request to address these?

(More information can be found in our pull request guide.)

[platinumazure]

Please add a unit test for this change.

[nzakas]

@ForbesLindesay can you please go back and fill in the PR template we have setup? The extra context helps.

[ForbesLindesay]

No, my previous experience of contributing to eslint has been terrible. Going through the process proved a waste of everyone's time.

I am providing this code under the WTF public license. Please feel free to do whatever you like with it. I provide it meerly to be a good open source citizen.

[nzakas]

I'm sorry you had a bad experience contributing in the past. Unfortunately, we can't do anything with a pull request that hasn't followed our contributor guidelines. In the future, if you feel that you'd like to let us know about a problem, please open an issue instead.

[nzakas]

Opened #7657 for further tracking.