public/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2025-12-07 01:23:55 +09:00
Code Issues Actions 7 Packages Projects Releases Wiki Activity

deps: update docs (#6462)

Browse Source
This commit is contained in:
Jason Rasmussen
2024-01-17 22:44:45 -05:00
committed by GitHub
parent 98cee8864d
commit 44873b4224
7 changed files with 6152 additions and 13360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/developer/testing.md
View File

@@ -10,7 +10,7 @@ Unit are run by calling `npm run test` from the `server` directory.
The backend has an end-to-end test suite that can be called with `npm run test:e2e` from the `server` directory. This will set up a dummy database inside a temporary container and run the tests against it. Setup and teardown is automatically taken care of. That test, however, can not set up all prerequisites to parse file formats, as that is very complex and error-prone. As such, this test excludes some test cases like HEIC file imports. The test suite will also print a friendly warning to remind you that not all tests are being run.
Note that there is a bug in nodejs <20.8 that causes segmentation faults when running these tests. If you run into segfaults, ensure you are using at least version 20.8.
Note that there is a bug in nodejs \<20.8 that causes segmentation faults when running these tests. If you run into segfaults, ensure you are using at least version 20.8.
To perform a full e2e test, you need to run e2e tests inside docker. The easiest way to do that is to run `make test-e2e` in the root directory. This will build and start a docker-compose consisting of the server, microservices, and a postgres database. It will then perform the tests and exit.