Files
directus/tests-blackbox
ian addb077d48 Emit action events with updated schema (#15576)
* Emit action events with updated schema

* Fix collections service consistency

* Pass action event upstream for createMany item

* Pass action event upstream when processing payload

* Skip unnecessary retrival of updated schema

* Fix folder tests

* Fields service consistency

* Prevent duplicate cache clearing when deleting fields

* Add tests_extensions_log table

* Update collections crud tests

* Add fields crud tests

* Add action verify schema tests

* Bypass system cache purge in relations service

* Bypass system cache purge in nested field deletion

* Update source for consistency when creating from collection
2022-11-15 10:02:45 -05:00
..
2022-07-15 15:25:32 +00:00
2022-07-15 15:25:32 +00:00
2022-07-15 15:25:32 +00:00
2022-07-15 15:25:32 +00:00
2022-07-15 15:25:32 +00:00
2022-07-15 15:25:32 +00:00

Blackbox tests

Setup

Make sure the containers for the databases are running by running docker compose up -d in this folder.

Running tests locally

Run npm run test:blackbox to run the blackbox tests for every supported database vendor.

Testing a specific database

Provide a csv of database drivers in the TEST_DB environment variable to test specific databases:

TEST_DB=cockroachdb npm run test:blackbox

Using an existing Directus instance

The test suite will spin up a fresh copy of the Directus API from the current build. To use an already running copy of Directus, set the TEST_LOCAL flag:

TEST_DB=cockroachdb TEST_LOCAL=true npm run test:blackbox

This will use localhost:8055 as the URL for every test. Note: make sure to connect your local Directus database instance to the test database container found in docker-compose in this folder.

Watching for (test) changes

Use npm run test:blackbox:watch to enable Jest's --watch mode, especially useful in combination with the flags above.

This does not watch changes to Directus; it only watches changes to the tests.