Sorry for the very big commit that may lead to git log issues and merge
conflicts, but it's a major step forward:

 * Server can be faster at startup because imports() are async and we can
   easily lazy import big modules
 * Angular doesn't seem to support ES import (with .js extension), so we
   had to correctly organize peertube into a monorepo:
    * Use yarn workspace feature
    * Use typescript reference projects for dependencies
    * Shared projects have been moved into "packages", each one is now a
      node module (with a dedicated package.json/tsconfig.json)
    * server/tools have been moved into apps/ and is now a dedicated app
      bundled and published on NPM so users don't have to build peertube
      cli tools manually
    * server/tests have been moved into packages/ so we don't compile
      them every time we want to run the server
 * Use isolatedModule option:
   * Had to move from const enum to const
     (https://www.typescriptlang.org/docs/handbook/enums.html#objects-vs-enums)
   * Had to explictely specify "type" imports when used in decorators
 * Prefer tsx (that uses esbuild under the hood) instead of ts-node to
   load typescript files (tests with mocha or scripts):
     * To reduce test complexity as esbuild doesn't support decorator
       metadata, we only test server files that do not import server
       models
     * We still build tests files into js files for a faster CI
 * Remove unmaintained peertube CLI import script
 * Removed some barrels to speed up execution (less imports)

2023-08-11 15:02:33 +02:00

2.8 KiB

Raw Blame History

Tests

Preparation

Prepare PostgreSQL user so PeerTube can delete/create the test databases:

sudo -u postgres createuser you_username --createdb --superuser

Prepare the databases:

npm run clean:server:test

Build PeerTube:

npm run build

Server tests

Dependencies

Run docker containers needed by some test files:

sudo docker run -p 9444:9000 chocobozzz/s3-ninja
sudo docker run -p 10389:10389 chocobozzz/docker-test-openldap

Ensure you also have these commands:

exiftool --help
parallel --help

Otherwise, install the packages. On Debian-based systems (like Debian, Ubuntu or Mint):

sudo apt-get install parallel libimage-exiftool-perl

Test

To run all test suites (can be long!):

npm run test # See scripts/test.sh to run a particular suite

To run a specific test:

npm run mocha -- --exit --bail packages/tests/src/your-test.ts

# For example
npm run mocha -- --exit --bail packages/tests/src/api/videos/single-server.ts

Configuration

Some env variables can be defined to disable/enable some tests:

DISABLE_HTTP_IMPORT_TESTS=true: disable import tests (because of youtube that could rate limit your IP)
ENABLE_OBJECT_STORAGE_TESTS=true: enable object storage tests (needs chocobozzz/s3-ninja container first)
AKISMET_KEY: specify an Akismet key to test akismet external PeerTube plugin
OBJECT_STORAGE_SCALEWAY_KEY_ID and OBJECT_STORAGE_SCALEWAY_ACCESS_KEY: specify Scaleway API keys to test object storage ACL (not supported by our chocobozzz/s3-ninja container)
ENABLE_FFMPEG_THUMBNAIL_PIXEL_COMPARISON_TESTS=true: enable pixel comparison on images generated by ffmpeg. Disabled by default because a custom ffmpeg version may fails the tests

Debug server logs

While testing, you might want to display a server's logs to understand why they failed:

NODE_APP_INSTANCE=1 NODE_ENV=test npm run parse-log -- --level debug | less +GF

You can also:

checkout only the latest logs (PeerTube >= 5.0):

tail -n 100 test1/logs/peertube.log | npm run parse-log -- --level debug --files -

continuously print the latests logs (PeerTube >= 5.0):

tail -f test1/logs/peertube.log | npm run parse-log -- --level debug --files -

Client E2E tests

Local tests

To run tests on local web browsers (comment web browsers you don't have in client/e2e/wdio.local.conf.ts):

PEERTUBE2_E2E_PASSWORD=password npm run e2e:local

Browserstack tests

To run tests on browser stack:

BROWSERSTACK_USER=your_user BROWSERSTACK_KEY=your_key npm run e2e:browserstack

Add E2E tests

To add E2E tests and quickly run tests using a local Chrome:

cd client/e2e
../node_modules/.bin/wdio wdio.local-test.conf.ts # you can also add --mochaOpts.grep to only run tests you want

2.8 KiB Raw Blame History