Cypress CLI execution - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cypress CLI command?

You run the command cypress run --spec cypress/e2e/login.cy.js in your terminal. What will Cypress do?

A Run all tests in the <code>login.cy.js</code> file and output results in the terminal.

B Open the Cypress Test Runner GUI and allow manual test selection.

C Run all tests in the <code>cypress/e2e</code> folder except <code>login.cy.js</code>.

D Run tests only in the <code>cypress/support</code> folder.

💡 Hint

The --spec flag specifies which test file to run in headless mode.

The cypress run command runs tests in headless mode. Using --spec limits the run to the specified test file. So, only tests in login.cy.js will run and results will show in the terminal.

❓ assertion

intermediate

Which assertion verifies Cypress CLI ran tests successfully?

After running cypress run, you want to check if all tests passed by inspecting the exit code. Which assertion is correct in a Node.js script?

Cypress

const { exec } = require('child_process');
exec('cypress run', (error, stdout, stderr) => {
  // Which assertion below correctly checks success?
});

A assert.strictEqual(error, null);

B assert.strictEqual(error.code, 1);

C assert.strictEqual(stderr.length, 0);

D assert.strictEqual(stdout.includes('failing'), true);

💡 Hint

A null error means the command exited with code 0 (success).

If error is null, the Cypress CLI command exited successfully with code 0, meaning all tests passed. Other options check for failure or incorrect conditions.

🔧 Debug

advanced

Why does cypress run --headless fail with 'No browser found' error?

You run cypress run --headless --browser chrome but get an error: No browser found named chrome. What is the most likely cause?

A You must specify the full path to the Chrome executable.

B Chrome browser is not installed or not detected on the system.

C The <code>--headless</code> flag is incompatible with Chrome.

D Cypress CLI requires <code>--browser chromium</code> instead of <code>chrome</code>.

💡 Hint

Cypress needs the browser installed to run tests in it.

The error means Cypress cannot find the Chrome browser installed on your machine. You must have Chrome installed and accessible in your system PATH for Cypress to run tests in it.

🧠 Conceptual

advanced

What does the --record flag do in Cypress CLI?

You run cypress run --record --key abc123. What is the purpose of the --record flag?

A It records video of the test run locally on your machine.

B It runs tests in parallel automatically on multiple machines.

C It enables verbose logging of all test steps in the terminal.

D It uploads test results to the Cypress Dashboard for detailed reporting.

💡 Hint

Think about Cypress Dashboard integration.

The --record flag sends test results to the Cypress Dashboard service, allowing you to see detailed reports, test history, and analytics online. It requires a valid project --key.

❓ framework

expert

In a CI pipeline, which Cypress CLI command best runs tests with video recording and fails the build on test failures?

You want to run Cypress tests in a CI environment. You want to record videos, upload results to Dashboard, and ensure the pipeline fails if any test fails. Which command is best?

A cypress run --record --key $CYPRESS_RECORD_KEY --video --exit

B cypress run --record --key $CYPRESS_RECORD_KEY --video --fail-fast

C cypress run --record --key $CYPRESS_RECORD_KEY --video

D cypress open --record --key $CYPRESS_RECORD_KEY --video

💡 Hint

Consider default Cypress CLI behavior on test failures.

The cypress run command by default exits with a non-zero code if tests fail, causing CI to fail. The --video flag enables video recording. The --record flag uploads results to Dashboard. --exit is deprecated and --fail-fast stops on first failure but is optional.