Either environment is not specified or specified with the unsupported environment. Please check

## Running Cucumber Test through Terminal (Command Prompt)

SYNTAX: npm run ccs_cucumber_test -- ENV={Env} [--FEATURES={Feature}] [--TAGS={tags}] [--BROWSER=] [--HEADLESS={true/false}] [--CLIENT={client}] [--REPORT_PATH={report_path}] [--PARALLEL_WORKER={Parallel_Worker_Count}>

- ENV is mandatory (required) argument. Value can be any one of the following: dev, test, qa, stage, ct, uat, prod

- If no FEATURES are specified then it will run all features

- If no TAGS are specified then it will run all scenarios of applicable features irrespective of tag

- If no BROWSER is specified then default would be Chrome. Value can be only Chrome or Firefox or Webkit

- If HEADLESS parameter is not specified then default would be Headless as false

- If REPORT_PATH parameter is specified then default Cucumber report HTML and JSON files will be generated in the specified folder

- If PARALLEL_WORKER parameter is specified then given number of parallel execution will happen. Otherwise it will be defaulted to 1

- The following will not work as ENV is mandatory

npm run ccs_cucumber_test

- To execute all of the features with PROD environment variables with Chrome browser

npm run ccs_cucumber_test -- --ENV=PROD

- To execute all of the features under loginPage folder with PROD environment variables with Chrome browser

npm run ccs_cucumber_test -- --ENV=PROD --FEATURES=app/test/features/loginPage

- To execute all of the features under loginPage and booksPage folder with PROD environment variables with Chrome browser

npm run ccs_cucumber_test -- --ENV=PROD --FEATURES=app/test/features/loginPage,app/test/features/booksPage

- To execute all of the features under loginPage folder which are tagged as @auth with PROD environment variables with Chrome browser

npm run ccs_cucumber_test -- --ENV=PROD --FEATURES=app/test/features/loginPage --TAGS="@auth"

- To execute all of the features which are tagged as @auth with PROD environment variables with Chrome browser

npm run ccs_cucumber_test -- --ENV=PROD --TAGS="@auth"

- To execute all of the features which are tagged as @auth or @add with PROD environment variables with Chrome browser

npm run ccs_cucumber_test -- --ENV=PROD --TAGS="@auth or @add"

- To execute all of the features which are not tagged as @auth with PROD environment variables with Chrome browser

npm run ccs_cucumber_test -- --ENV=PROD --FEATURES=app/test/features/loginPage --TAGS="not @auth"

- To execute all of the features with PROD environment variables with Firefox

npm run ccs_cucumber_test -- --ENV=PROD --BROWSER=Firefox

- To execute all of the features with PROD environment variables with Webkit

npm run ccs_cucumber_test -- --ENV=PROD --BROWSER=Webkit

- To execute all of the features with PROD environment variables with browser as Headless

npm run ccs_cucumber_test -- --ENV=PROD --BROWSER=Webkit --HEADLESS=true

- To execute all of the features with PROD environment variables with browser as Headless and to generate the Report at downloads folder

npm run ccs_cucumber_test -- --ENV=PROD --BROWSER=Webkit --HEADLESS=true --REPORT_PATH=C:/users/Test/Downloads

- To execute all of the features with PROD environment variables with browser as Headless in Parallel mode

npm run ccs_cucumber_test -- --ENV=PROD --BROWSER=Webkit --HEADLESS=true --PARALLEL_WORKER=2

## Running Playwright Test through Terminal (Command Prompt)

SYNTAX: npm run ccs_playwright_test -- ENV={Env} [--TEST_DIR={test_dir}] [--TAGS={tags}] [--BROWSER=] [--HEADLESS={true/false}] [--CLIENT={client}] [--REPORT_PATH={report_path}] [--PARALLEL_WORKER={Parallel_Worker_Count}> [RETRY_COUNT={retry_count}] [REPEAT_EACH={repeat_each}] [REPORTER={reporter}] [TIME_OUT={timetout}]

- ENV is mandatory (required) argument. Value can be any one of the following: dev, test, qa, stage, ct, uat, prod

- If no FEATURES are specified then it will run all features

- If no TAGS are specified then it will run all scenarios of applicable features irrespective of tag

- If no BROWSER is specified then default would be Chrome. Value can be only Chrome or Firefox or Webkit

- If HEADLESS parameter is not specified then default would be Headless as false

- If REPORT_PATH parameter is specified then default Cucumber report HTML and JSON files will be generated in the specified folder

- If PARALLEL_WORKER parameter is specified then given number of parallel execution will happen. Otherwise it will be defaulted to 1

- If REPEAT_EACH parameter is not specified then default would be 1. If specified then every tests will run given no. of times

- If RETRY_COUNT parameter is not specified then default would be 1. If specified then given number of times failed tests will be re-executed

- If TIME_OUT parameter is not specified then default would be 1. If specified then given timetout value is utilized for each tests

- The following will not work as ENV is mandatory

npm run ccs_playwright_test

- To execute all of the features with PROD environment variables with Chrome browser

npm run ccs_playwright_test -- --ENV=PROD

- To execute all of the features under loginPage folder with PROD environment variables with Chrome browser

npm run ccs_playwright_test -- --ENV=PROD --FEATURES=app/test/features/loginPage

- To execute all of the features under loginPage and booksPage folder with PROD environment variables with Chrome browser

npm run ccs_playwright_test -- --ENV=PROD --FEATURES=app/test/features/loginPage,app/test/features/booksPage

- To execute all of the features under loginPage folder which are tagged as @auth with PROD environment variables with Chrome browser

npm run ccs_playwright_test -- --ENV=PROD --FEATURES=app/test/features/loginPage --TAGS="@auth"

- To execute all of the features which are tagged as @auth with PROD environment variables with Chrome browser

npm run ccs_playwright_test -- --ENV=PROD --TAGS="@auth"

- To execute all of the features which are tagged as @auth or @add with PROD environment variables with Chrome browser

npm run ccs_playwright_test -- --ENV=PROD --TAGS="@auth|@add"

- To execute all of the features which are not tagged as @auth with PROD environment variables with Chrome browser

npm run ccs_playwright_test -- --ENV=PROD --FEATURES=app/test/features/loginPage --TAGS="'^(?!.*@myTag).*'"

- To execute all of the features with PROD environment variables with Firefox

npm run ccs_playwright_test -- --ENV=PROD --BROWSER=Firefox

- To execute all of the features with PROD environment variables with Webkit

npm run ccs_playwright_test -- --ENV=PROD --BROWSER=Webkit

- To execute all of the features with PROD environment variables with browser as Headless

npm run ccs_playwright_test -- --ENV=PROD --BROWSER=Webkit --HEADLESS=true

- To execute all of the features with PROD environment variables with browser as Headless and to generate the Report at downloads folder

npm run ccs_playwright_test -- --ENV=PROD --BROWSER=Webkit --HEADLESS=true --REPORT_PATH=C:/users/Test/Downloads

- To execute all of the features with PROD environment variables with browser as Headless in Parallel mode

npm run ccs_playwright_test -- --ENV=PROD --BROWSER=Webkit --HEADLESS=true --PARALLEL_WORKER=2