https://cypress.io logo
Hi, I started using parallelization for my e2e cyp...
# best-practices
a
Hi, I started using parallelization for my e2e cypress tests in
aws code build
, i did setup build spec and given 3 machines to run in parallel, but the thing is when i run all the tests, it took nearly 30 mins build time each(unbearable cost), which includes installing of node modules and server start time in each machine, and got separate cypress json's for machine. how to overcome this, is there any best practice to fix this build time
Copy code
yml
version: 0.2
batch:
   fast-fail: true
   build-matrix:
      static:
         ignore-failure: false
         env:
            privileged-mode: true
      dynamic:
         env:
            variables:
               WORKERS:
                  - 1
                  - 2
                  - 3
phases:
   install:
      commands:
         - node --version
         - export COMMIT_INFO_BRANCH="$(git rev-parse HEAD | xargs git name-rev | cut -d' ' -f2 | sed 's/remotes\/origin\///g')"
         - export COMMIT_INFO_MESSAGE="$(git log -1 --pretty=%B)"
         - export COMMIT_INFO_EMAIL="$(git log -1 --pretty=%ae)"
         - export COMMIT_INFO_AUTHOR="$(git log -1 --pretty=%an)"
         - export COMMIT_INFO_SHA="$(git log -1 --pretty=%H)"
         - export COMMIT_INFO_REMOTE="$(git config --get remote.origin.url)"
         
   pre_build:
      commands:
         - npm install cypress --save-dev

   build:
      commands:
         - yarn install
         - yarn start & npx wait-on http://localhost:3000
         - yarn cypress run