From a92c416d8caf46c5a7f97cb8779e851ef2378ba8 Mon Sep 17 00:00:00 2001 From: Tim Otten Date: Tue, 26 Apr 2016 13:12:38 -0700 Subject: [PATCH] Update CONTRIBUTING.md --- .github/CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 59ba04f559..9a1e22a5d8 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -55,9 +55,9 @@ Pull-requests are tested automatically by a build-bot. Key things to know: * The console output. If the test-suite encountered a significant error (such as a PHP crash), the key details will only appear in the console. * Code-style tests are executed first. If the code-style in this patch is inconsistent, the remaining tests will be skipped. - * The primary tests may take 20-120 min to execute. This includes the following suites: `api_v3_AllTests`, `CRM_Core_AllTests`, `Civi\AllTests`, `civicrm-upgrade-test`, and `karma` - * Some tests are run separately. These tests are not reported by the PR buildbot: `CRM_AllTests`, `WebTest_AllTests` + * The primary tests may take 20-120 min to execute. This includes the following suites: `api_v3_AllTests`, `CRM_AllTests`, `Civi\AllTests`, `civicrm-upgrade-test`, and `karma` * There are a handful of unit tests which are time-sensitive and which fail sporadically. See: https://forum.civicrm.org/index.php?topic=36964.0 + * The web test suite (`WebTest_AllTests`) takes several hours to execute. [It runs separately -- after the PR has been merged.](https://test.civicrm.org/job/CiviCRM-WebTest-Matrix/) For detailed discussion about automated tests, see http://wiki.civicrm.org/confluence/display/CRMDOC/Testing -- 2.25.1