1e6f4ba340
no issue - Admin API v2 returned /404/, see comment in code base: /** * CASE: admin api should serve preview urls * * @NOTE * The url service has no clue of the draft/scheduled concept. It only generates urls for published resources. * Adding a hardcoded fallback into the url service feels wrong IMO. * * Imagine the site won't be part of core and core does not serve urls anymore. * Core needs to offer a preview API, which returns draft posts. * That means the url is no longer /p/:uuid, it's e.g. GET /api/v2/content/preview/:uuid/. * /p/ is a concept of the site, not of core. * * The site is not aware of existing drafts. It won't be able to get the uuid. * * Needs further discussion. */ |
||
---|---|---|
.. | ||
old | ||
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