Cypress CLI execution - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run Cypress tests in headless mode.

Cypress

npx cypress run --[1]

Drag options to blanks, or click blank then click option'

Adebug

Bopen

Cheadless

Dwatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using --open runs Cypress with the UI, not headless.

Using --debug or --watch are not valid Cypress CLI flags.

The --headless flag runs Cypress tests without opening the browser UI, suitable for automated environments.

2fill in blank

medium

Complete the command to specify the browser as Chrome when running Cypress tests.

Cypress

npx cypress run --browser [1]

Drag options to blanks, or click blank then click option'

Afirefox

Bedge

Csafari

Dchrome

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting browsers not installed or unsupported may cause errors.

Using uppercase letters in browser name can cause issues; use lowercase.

The --browser chrome option tells Cypress to run tests using the Chrome browser.

3fill in blank

hard

Fix the error in the command to run Cypress tests with a specific spec file.

Cypress

npx cypress run --spec [1]

Drag options to blanks, or click blank then click option'

Acypress/integration/test_spec.js

B"cypress/integration/test_spec.js"

C'cypress/integration/test_spec.js'

Dcypress/integration/test_spec

Attempts:

3 left

💡 Hint

Common Mistakes

Including quotes around the spec path causes errors.

Omitting the file extension leads to file not found errors.

The --spec option requires the file path without quotes for correct CLI parsing.

4fill in blank

hard

Fill both blanks to run Cypress tests in headed mode and record the run.

Cypress

npx cypress run --[1] --[2]

Drag options to blanks, or click blank then click option'

Aheaded

Brecord

Cheadless

Dopen

Attempts:

3 left

💡 Hint

Common Mistakes

Using --headless instead of --headed when UI is needed.

Forgetting to add --record when wanting to save test results.

Use --headed to run tests with the browser UI visible, and --record to save the test run results to Cypress Dashboard.

5fill in blank

hard

Fill all three blanks to run Cypress tests with a specific config file, in headless mode, and using Firefox browser.

Cypress

npx cypress run --config-file [1] --[2] --browser [3]

Drag options to blanks, or click blank then click option'

Acypress.prod.json

Bheadless

Cfirefox

Dcypress.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using default config file when a specific one is needed.

Mixing up browser names or modes.

Adding quotes around file names or flags.

The --config-file option specifies which config file to use, --headless runs tests without UI, and --browser firefox runs tests in Firefox.

Practice

1. What does running cypress run from the command line do?

easy

A. Runs all tests in headless mode without opening the Cypress UI

B. Opens the Cypress Test Runner UI for manual test selection

C. Starts a web server for the application under test

D. Generates a test report without executing tests

Solution

1. Step 1: Understand the command cypress run

   This command runs Cypress tests from the command line without opening the UI.

2. Step 2: Identify the mode of execution

   By default, cypress run runs tests in headless mode, meaning no browser window appears.

3. Final Answer:

   Runs all tests in headless mode without opening the Cypress UI -> Option A

4. Quick Check:

   cypress run = headless test run [OK]

Hint: Remember: 'run' means headless test execution [OK]

Common Mistakes:

• Confusing 'cypress run' with 'cypress open'
• Thinking it opens the UI
• Assuming it starts a server

2. Which of the following is the correct syntax to run Cypress tests in Chrome browser using CLI?

easy

A. cypress run --browser chrome

B. cypress open --browser chrome

C. cypress run -b firefox

D. cypress start --browser chrome

Solution

1. Step 1: Identify the correct command to run tests in CLI

   cypress run is used to run tests from CLI, not cypress open or cypress start.

2. Step 2: Check the correct option for specifying browser

   The option to specify browser is --browser, so cypress run --browser chrome is correct syntax.

3. Final Answer:

   cypress run --browser chrome -> Option A

4. Quick Check:

   Use --browser with cypress run [OK]

Hint: Use 'cypress run --browser' to specify browser [OK]

Common Mistakes:

• Using 'cypress open' instead of 'cypress run' for CLI execution
• Using wrong option '-b' instead of '--browser'
• Using non-existent command 'cypress start'

3. What will be the output when running cypress run --spec "cypress/e2e/login.cy.js"?

medium

A. Runs all tests except those in login.cy.js

B. Runs only the tests inside login.cy.js and shows results in terminal

C. Opens Cypress UI and highlights login.cy.js tests

D. Throws an error because --spec is invalid

Solution

1. Step 1: Understand the --spec option

   The --spec option tells Cypress to run only the specified test file(s).

2. Step 2: Analyze the command behavior

   The command runs tests only in cypress/e2e/login.cy.js and outputs results in the terminal because cypress run is headless.

3. Final Answer:

   Runs only the tests inside login.cy.js and shows results in terminal -> Option B

4. Quick Check:

   --spec runs specified test file only [OK]

Hint: Use --spec to run specific test files [OK]

Common Mistakes:

• Thinking it runs all tests except specified file
• Expecting Cypress UI to open with 'run' command
• Assuming --spec is invalid option

4. You run cypress run --browser chrome --headed but tests still run headless. What is the likely cause?

medium

A. Cypress does not support headed mode with Chrome

B. The Chrome browser is not installed on the machine

C. The command must include --headless to run headed

D. The --headed flag is misspelled or missing

Solution

1. Step 1: Understand the --headed flag

   The --headed flag runs tests with the browser UI visible, not headless.

2. Step 2: Identify why tests run headless despite --headed

   The likely cause is that the --headed flag was misspelled (e.g., --headless) or missing from the actual command executed. cypress run defaults to headless mode without the correct flag.

3. Final Answer:

   The --headed flag is misspelled or missing -> Option D

4. Quick Check:

   Missing or misspelled --headed defaults to headless [OK]

Hint: Verify --headed flag spelling and presence when headed mode fails [OK]

Common Mistakes:

• Confusing --headed with --headless
• Assuming Cypress doesn't support headed Chrome
• Ignoring browser installation status

5. You want to run tests only in Firefox, headlessly, and save the results to a JSON file named results.json. Which command achieves this?

hard

A. cypress open --browser firefox --headless --output results.json

B. cypress run --browser firefox --headed --reporter json --output results.json

C. cypress run --browser firefox --headless --reporter json --reporter-options output=results.json

D. cypress run --browser firefox --headless --output results.json

Solution

1. Step 1: Choose correct command and browser

   Use cypress run to run tests headlessly and specify --browser firefox.

2. Step 2: Specify headless mode and JSON reporter output

   Use --headless for no UI, --reporter json to format output, and --reporter-options output=results.json to save results.

3. Final Answer:

   cypress run --browser firefox --headless --reporter json --reporter-options output=results.json -> Option C

4. Quick Check:

   Use reporter options to save JSON results [OK]

Hint: Use --reporter and --reporter-options to save JSON output [OK]

Common Mistakes:

• Using 'cypress open' instead of 'cypress run'
• Missing --reporter or reporter-options flags
• Confusing --headed with --headless