This CI step takes 10+ minutes now. It's slow because all the tests run in-band (serial rather than in parallel) so that they don't clobber each other's postgres db.
The tests could be made to ran in parallel by having them use their own temporary postgres schema (a container/namespace within a database).
One approach is to create a jest setupFilesAfterEnv script that configures PG_SCHEMA:
This CI step takes 10+ minutes now. It's slow because all the tests run in-band (serial rather than in parallel) so that they don't clobber each other's postgres db.
The tests could be made to ran in parallel by having them use their own temporary postgres schema (a container/namespace within a database).
One approach is to create a jest
setupFilesAfterEnv
script that configuresPG_SCHEMA
: