Use paratest for parallel test execution #5372
Conversation
manuelmeister
force-pushed
the
feature/parallel-api-test
branch
from
d4a111d
to
151eb79
Compare
manuelmeister
force-pushed
the
feature/parallel-api-test
branch
from
151eb79
to
4d750bc
Compare
manuelmeister
requested review from
carlobeltrame,
BacLuc and
usu
and removed request for
BacLuc
|
@usu Yes, but you would need to setup the databases |
|
I realized that from 39410e3 (update phpunit from v10.5.20 to v10.5.21, main feature: sebastianbergmann/phpunit#5861) the test only takes 3m 19s, instead of 14m 34s. |
There was a problem hiding this comment.
Please revert the unnecessary change and the change in dev/doctrine.yaml, and i am happy.
Tested it locally, and it ran out of memory when it tried to merge the coverage.
But most of us will anyway not run the tests locally anymore, it takes too much time.
But running the tests locally without paratest still works
| POSTGRES_PASSWORD: 'ecamp3' | ||
| POSTGRES_USER: 'ecamp3' | ||
| POSTGRES_DB: 'ecamp3test' |
There was a problem hiding this comment.
please revert this unnecessary change.
Else future devs might think that this change is needed.
| doctrine: | ||
| dbal: | ||
| # "TEST_TOKEN" is typically set by ParaTest | ||
| dbname_suffix: 'dev%env(default::TEST_TOKEN)%' |
There was a problem hiding this comment.
i don't think you need the test token for dev
|
It seems to be stable, tested it 20 times:
|
To speed up our api tests, I've parallelized them with paratest. It works quite good. Has to be tested, if it actually tests, as the duration seems fishy