parallel execution

[kevgo]

what

• running activities concurrently

why

• faster execution
• more robust tests that model the dependencies between tests explicitly

how

• activities defined via parallel are run concurrently
• allow defining groups of activities that execute sequentially: files in alphabetical order, activities as defined in the files
• activities are referenced as: <filename>: <activity names regex>. Omitting the activity names means all activities in that file.
• could use https://www.npmjs.com/package/jest-worker for this

examples

Test all .md files in the repo concurrently:

parallel: true

Test only particular files and folders:

parallel:
  - .
  - documentation

Exclude certain folders:

parallel: true
exclude: 
  - vendor

Run all activities in the tutorial folder sequentially, the rest concurrently:

parallel: true
sequential-folders:
  - tutorial

Sequentially run all activities in the setup folder, then all activities in the tutorial folder:

parallel: true
sequential-folders:
  - setup
  - tutorial

Run all activities in each file in documentation sequentially, but files in parallel:

parallel: true
sequential-files:
  - documentation

Run all start-server, verify-server-runs, and stop-server activities in sequence, in the order they are defined in the documentation:

parallel: true
sequential-activities:
  - start-server
  - verify-server-runs
  - stop-server

Run everything sequentially, as before:

sequential-folders:
  - .
  - tutorial