documentation on testing and integrations about usrse.github.io

[vsoch]

The tests are self documenting in that (given that they exist) they run, and in that something doesn't work, it will issue an error. In the case of credentials or custom settings in CircleCI I could see the need to document this, however this repository has no special settings or secrets, everything that is needed is represented in the .circleci/config.yml and .github/workflows. In the case that changes (e.g., some external integration is added or a secret / permission is needed, we can re-address this issue).

[vsoch]

Actually, let me flip this suggestion on its head! What I think would be useful to do is to append the already existing notes with a comment that there aren't any secrets or permissions to be worried about. I'll also re-organize into sections for each of Travis, CircleCI, and GitHub. That should meet the requirements of this request.

[vsoch]

Putting myself in the shoes of someone not familiar with the testing, this is how I see it playing out:

Currently

• some security breach / thing is announced
• "Oh no, I think usrse.github.io uses that!"
• arrives at repo, no notes (panic)

With Updates

• some security breach / thing is announced
• "Oh no, I think usrse.github.io uses that!"
• arrives at repo, see notes, no cause for alarm.

I need to shower / meeting / finish something for a deadline but I'll do this soon too.

[vsoch]

I'll work on this after #102 is properly reviewed.