Update: Why does my test fail on the testbot, with new testbot and Drupal 8 info

Problem/Motivation

https://www.drupal.org/project/testbot
is the project page for
Drupal.org Testbots
and is linked from the irc factoid: testbot?

testbot is  Drupal.org's patch QA (a.k.a "testbot") is composed of several projects. For details, or for help troubleshooting testbot issues, see: http://drupal.org/project/testbot | See testbot health at http://qa.drupal.org

The text there is out of date (with regards to Drupal 8)

Proposed resolution

• split out the generic info
• isolate Drupal 7 info
• make a Drupal 8 section

Remaining tasks

• draft an update (use the issue summary here)
• verify the accuracty

User interface changes

text before

<b>Why does my test fail on the testbot but works OK locally?</b> There are probably three key differences between your local test environment and the testbot <ul>
<li>The testbot is running PHP 5.3.27 (from dotdeb)</li>
<li>The testbot has clean URLs turned off by default (as does Drupal)</li>
<li>The testbot webroot is in a subdirectory (like http://drupaltestbot.osuosl.test/checkout/?q=admin)</li>
<li>The testbot runs tests using run-tests.sh. Try using that technique and see if your tests succeeeds</li>
<li>The testbot has to be able to run through the install process, then log in and enable simpletest and visit the testing page, all using the web UI. Have you tried that?</li>
<li>The testbot starts with all modules disabled and the tests themselves enable them. Disable your relevant modules so that they're not active locally before running local tests to get a reasonable result.</li>
<li>The testbot uses the issue version to determine which codebase to test against. Ensure the issue the patch has been uploaded to is set to a -dev release, as opposed to a specific release checkout.</li>
<li>If you get "failed to apply", check that the issue is set to the *branch*, not a specific tag. For example, an issue with a patch should be set to "7.x-1.x-dev", not "7.x-1.3". Try to apply the patch to a local repository just to make sure. If it fails on the testbot, it will fail locally too, if you're using "git apply".</li>
<li>If installation is failing, please try installing Drupal with your patch applied. Your patch may cause a failure in the installation.</li>
</ul>

API changes

NA