47db8e5d2f
* Clean-up api - Remove unnecessary deps - rimraf -> del-cli * Clean-up app - bytes -> pretty-bytes - Remove ms as we already have pretty-ms - Remove other unnecessary deps - Add storybook build to gitignore * Clean-up drive packages - Simplify cleanup scripts - rimraf -> del-cli - Remove unnecessary deps * Clean-up schema - Remove unnecessary dep (lodash) - Replace 'npm-watch' with native watch mode * Clean-up shared - Remove unnecessary dep (c8, adding @vitest/coverage-c8 will be addressed in other PR) - rimraf -> del-cli - npm-run-all -> concurrently * Clean-up root - Add missing eslint-plugin-jest dep - listr -> listr2 * Make build output a bit friendlier * Remove cleanup scripts Co-authored-by: Rijk van Zanten <rijkvanzanten@me.com>
E2E tests
Setup
Make sure the containers for the databases are running by running docker compose up -d in this folder.
Running tests locally
Run pnpm test:e2e to run the e2e 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 pnpm test:e2e
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 pnpm test:e2e
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 pnpm test:e2e: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.