Using parallel build in end to end tests
The docker-compose build used in E2E tests was running builds sequentially. This is an attempt to run the builds in parallel to optimize the E2E startup time. Before this commit, the "Start WorkAdventure" step takes 7m11 on GitHub
This commit is contained in:
parent
1181187271
commit
560be9b0d6
4
.github/workflows/end_to_end_tests.yml
vendored
4
.github/workflows/end_to_end_tests.yml
vendored
@ -23,8 +23,10 @@ jobs:
|
|||||||
run: npx playwright install --with-deps
|
run: npx playwright install --with-deps
|
||||||
- name: 'Setup .env file'
|
- name: 'Setup .env file'
|
||||||
run: cp .env.template .env
|
run: cp .env.template .env
|
||||||
|
- name: Build WorkAdventure
|
||||||
|
run: docker-compose -f docker-compose.yaml -f docker-compose.e2e.yml build --parallel
|
||||||
- name: Start WorkAdventure
|
- name: Start WorkAdventure
|
||||||
run: docker-compose -f docker-compose.yaml -f docker-compose.e2e.yml up -d --build
|
run: docker-compose -f docker-compose.yaml -f docker-compose.e2e.yml up -d
|
||||||
- name: Wait for environment to Start
|
- name: Wait for environment to Start
|
||||||
run: sleep 60
|
run: sleep 60
|
||||||
- name: Run Playwright tests
|
- name: Run Playwright tests
|
||||||
|
Loading…
Reference in New Issue
Block a user