diff options
| author | Thomas Steur <thomas.steur@googlemail.com> | 2014-10-05 10:40:06 +0400 |
|---|---|---|
| committer | Thomas Steur <thomas.steur@googlemail.com> | 2014-10-05 10:40:06 +0400 |
| commit | 5a61c09733bb7912711b804ce91652d111e00169 (patch) | |
| tree | 74387a08cc53fd64e167dfa90b3541b0fc3a3161 /tests/README.md | |
| parent | f34a13eacb6c2aabeb1ed16432a053fe44e982ec (diff) | |
refs #5940 databaseTestCase => integrationTestCase. Fixed some mentions of integration => system
Diffstat (limited to 'tests/README.md')
| -rw-r--r-- | tests/README.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/tests/README.md b/tests/README.md index 865606c12e..24b2699b43 100644 --- a/tests/README.md +++ b/tests/README.md @@ -1,4 +1,4 @@ -Piwik comes with unit tests, integration tests, Javascript tests and Webtests. +Piwik comes with unit tests, integration tests, system tests, Javascript tests and UI tests. This document briefly describes how to use and modify Piwik tests. ## Continuous Integration @@ -71,22 +71,22 @@ To execute the tests: 4. Run the tests $ cd /path/to/piwik/tests/PHPUnit - $ phpunit --group Core - $ phpunit --group Plugins - $ phpunit --group Integration + $ phpunit --testsuite CoreTests + $ phpunit --testsuite PluginTests + $ phpunit --testsuite SystemTests - There are three main groups of tests: Core, Plugins and Integration + There are also two main groups of tests: Core and Plugins For example run `phpunit --group Core` to run all Core Piwik tests. 5. Write more tests :) See ["Writing Unit tests with PHPUnit"](http://www.phpunit.de/manual/current/en/writing-tests-for-phpunit.html) -## Integration Tests +## System Tests -Integration tests files are in `tests/PHPUnit/Integration/*Test.php` +System tests files are in `tests/PHPUnit/Integration/*Test.php` -Integration tests allow to test how major Piwik components interact together. +System tests allow to test how major Piwik components interact together. A test will typically generate hits to the Tracker (record visits and page views) and then test all API responses and for each API output. It then checks that they match expected XML (or CSV, json, etc.). If a test fails, you can compare the processed/ and expected/ directories in a graphical @@ -102,7 +102,7 @@ Otherwise, if you didn't expect to modify the API outputs, it might be that your ### Scheduled Reports Tests -As part of our integration tests we generate the scheduled reports (in HTML, PDF & SMS). +As part of our system tests we generate the scheduled reports (in HTML, PDF & SMS). Some of these scheduled reports contain PNG graphs. Depending on the system under test, generated images can differ. Therefore, PNG graphs are only tested and compared against "expected" graphs, if the system under test has the same characteristics as the integration server. The characteristics of the integration server are described in `SystemTestCase::canImagesBeIncludedInScheduledReports()` |