Document LORIS automated testing

[johnsaigle]

Brief summary of changes

Adds a document that gives a high-level overview of our TravisCI pipeline.

This is intended as a general explainer of each of the tools we use. It will not include a list of each and every rule enforced by different tools nor provide example issues and solutions. Instead, links will be provided to the repositories of those tools as they'll be able to provide better detail than we can.

Content adapted from my presentation "How To Win The Love Of Travis".

Links to related tickets (GitHub, Redmine, ...)

• Resolves [Wiki] Explain the test suite for developers #5819

[christinerogers]

This is great.
PHPCS and PHPMD, as well as the don't say simply tool, could/should be written up under another file (Automated PR Checks.md or Automated Tools?), given their role is more like code sniff/review processes than Automated Testing of the code.

[johnsaigle]

I'll add a line for alex.js ("don't say simply" tool).

I'd rather keep phpcs and phpmd in this file. I'm looking at the document as being a place to send people when they're like "What is Travis, why is is failing" and this covers everything that Travis does. Whether something fails a test or is a style issue, both trigger the same kind and severity of problem from the perspective of someone trying to get a PR merged.

[johnsaigle]

@christinerogers I added a line for alex.js in the main PR discussing that tool. #5789

Since it won't actually be enforced in our automated testing suite (i.e. Travis), I think it's more appropriate in the Style Guide document.

[johnsaigle]

This may need updating after #5871

[christinerogers]

Last summer Alex Livadas wrote some text for developers in anticipation of these 99 - Developers pages.

@johnsaigle - any content from Alex's General Dev Troubleshooting Guide doc
or Unit Testing 101 that could be added?

cc @AlexandraLivadas

[johnsaigle]

The general troubleshooting guide isn't really relevant here.

The other document you linked is deprecated as it's been converted into the UnitTestingGuide, which is already linked in the Unit Testing section of this document.

suggested changes accepted

[kchatpar]

LGTM.

[driusan]

LGTM