diff options
| author | mattab <matthieu.aubry@gmail.com> | 2014-12-17 07:55:41 +0300 |
|---|---|---|
| committer | mattab <matthieu.aubry@gmail.com> | 2014-12-17 07:55:41 +0300 |
| commit | b3e41e199becde3fd1697e28dc4ace4a2c03f017 (patch) | |
| tree | ea1c3c4bf26526ec95dc30608564ae51ea13af21 | |
| parent | 759d55d39fa4e490445a92612126621173f05bf6 (diff) | |
Small typo
| -rw-r--r-- | tests/README.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/tests/README.md b/tests/README.md index ad91884fd0..57c9c0923b 100644 --- a/tests/README.md +++ b/tests/README.md @@ -128,9 +128,13 @@ We also have an OmniFixture that includes all other Fixtures. OmniFixture is use Remember to update the [Omnifixture SQL dump](https://github.com/piwik/piwik/blob/master/tests/resources/OmniFixture-dump.sql.gz) whenever you make any change to any fixture. For instance use: - ./console tests:setup-fixture OmniFixture --sqldump=OmniFixture-dump.sql` and then gzip. + ./console tests:setup-fixture OmniFixture --sqldump=OmniFixture-dump.sql + +and then gzip. -Keeping the OmniFixture up to date makes it easier to see which tests fail after each small fixture change. If we don't update the OmniFixture then we end up with many failed screenshots tests which makes it hard to see whether those changes are expected or not. +Keeping the OmniFixture up to date makes it easier to see which tests fail after each small fixture change. + +If we don't update the OmniFixture then we end up with many failed screenshots tests which makes it hard to see whether those changes are expected or not. ### Scheduled Reports Tests |