README.md

Application for running api or end-to-end automated tests in jenkins using puppeteer, jest, docker

build or pull image

docker build --network=host -t mhuretski/puppet-jest-es6 .
docker pull mhuretski/puppet-jest-es6

start in jenkins

1. Create pipeline

2. Specify repository from SCM

3. Run job

start in nodejs locally

npm test --forceExit --runInBand --
--ENV_TO_CHECK=<LOCAL> --BUILD_NUMBER=<BUILD_NUMBER> <SPEC> --CHECK=<UI> --SCREENSHOT=<SCREENSHOT> --debug
<LOCAL> - local environment (options: LOCAL DEV STAGE PROD)
<BUILD_NUMBER> - specifies folder for output
<SPEC> - specifies filename pattern to run 
    options: 
    - TEST - all patterns are executed
    - SPEC UI PERF - only files with those names are executed
    - API - pattern for files: api rest soap
<UI> - specifies how to check, preconditions are different
    for example, 'UI' is executed with browser, when API does not
    options: 'UI', 'API', 'REST', 'SOAP', 'SPEC', 'PERF', 'TEST'
<SCREENSHOT> - specifies whether to make screenshots
--debug - run non-headless

Example

npm test --forceExit --runInBand -- --ENV_TO_CHECK=LOCAL --BUILD_NUMBER=100 spec --CHECK=UI --debug --SCREENSHOT=true

Simplified Example

npm run local

In docker

docker create --name=LOCAL_TEST_SPEC \
  -v $(pwd)/result:/app/result \
  -v $(pwd)/src:/app/src \
  -v $(pwd)/tests:/app/tests \
  --user $(id -u):$(id -g) \
  --network=host \
  mhuretski/puppet-jest-es6 \
  npm test \
  --silent \
  --forceExit \
  --runInBand \
  -- \
  --ENV_TO_CHECK=LOCAL \
  --BUILD_NUMBER=100 \
  SPEC \
  --CHECK=SPEC \
  --SCREENSHOT=true

IDE scope setup pattern:

file:tests//*&&(file:*ui.ts||file:*spec.ts||file:*api.ts||file:*soap.ts||file:*rest.ts||file:*perf.ts)