Ghost

History

Nazar Gargol 3c7af7e6f0 Fixed accepnatce test failure no issue - Initial commit that broke the build: `20cce5da37` - There is no enforced ordering for integrations and because of combined differences how MySQL/SQLite orders by default in combination with how created_at/updated_at dates are generated for fixtures in tests and for migrations there is no reliable way to check order	2019-07-22 17:12:43 +02:00
..
old	Fixed accepnatce test failure	2019-07-22 17:12:43 +02:00
README.md

Nazar Gargol 3c7af7e6f0 Fixed accepnatce test failure

no issue

- Initial commit that broke the build: 20cce5da37
- There is no enforced ordering for integrations and because of combined differences how MySQL/SQLite orders by default in combination with how created_at/updated_at dates are generated for fixtures in tests and for migrations there is no reliable way to check order

2019-07-22 17:12:43 +02:00

old Fixed accepnatce test failure 2019-07-22 17:12:43 +02:00

README.md

Acceptance Tests

This folder should only contain a set of basic API use cases.

We are currently refactoring the test env. The "old" folder currently contains all API tests for the stable API version (v2). The goal is:

either keep a test if it's a basic use case e.g. upload an image, schedule a post, download a theme
otherwise move the test to regression api v2 tests

We probably need a differentiation for the acceptance tests for session and api_key authentication.

Before we move tests:

we have to re-work how are test utility is structured
we have to reduce tests