Ghost/test/regression/README.md

## Regression Tests

This folder should contain packages which we test in a cron job once per day.
These tests should ensure that we don't break Ghost.

The goal is that most of these packages use Ghost's API's to test behaviours, otherwise transform the tests into unit tests.
Separated test env into: acceptance, regression and unit tests (#10411) refs #9178 `yarn test` only runs acceptance and unit tests. We will setup a cronjob in Travis and run the regression tests once per day. You can manually run them with `yarn test:regression` This separation is just a first step into the right direction. Travis will no longer run for 10-13minutes. The goal is to run common API use cases and unit tests in Travis and locally by default. ## After this separation we still need to: - re-work our test utility - remove some tests - define which tests are our common API use cases - rewrite some tests - make testing easier (starting/stopping Ghost, fixtures and resetting services or event listeners, it's a pain and takes sometimes ages to fix tests) --- Acceptance: - common/basic API use cases against the current stable API Unit: - all unit tests (no database access) - proper mocking Regression: - packages we don't want to run for each PR or commit - tests which protect Ghost from breaking components and behaviour - it is wishful that regression tests are using Ghost's API's (frontend, apps, core) --- This PR requires an update to our docs. 2019-01-22 19:54:50 +03:00			`## Regression Tests`

			`This folder should contain packages which we test in a cron job once per day.`
			`These tests should ensure that we don't break Ghost.`

			`The goal is that most of these packages use Ghost's API's to test behaviours, otherwise transform the tests into unit tests.`