Cypress Dashboard (Cloud) service - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of the Cypress Dashboard (Cloud) service?

Choose the best description of what the Cypress Dashboard (Cloud) service provides for test automation.

A It is a local server that runs Cypress tests on your machine.

B It provides a database for storing application data during tests.

C It is a code editor specialized for writing Cypress tests.

D It stores and visualizes test run results, providing insights and debugging tools.

💡 Hint

Think about where test results and logs are stored and viewed remotely.

The Cypress Dashboard (Cloud) service collects and displays test run results, screenshots, and videos to help teams analyze and debug tests.

🎯 Scenario

intermediate

How to enable recording test runs to Cypress Dashboard?

You want to record your Cypress test runs to the Dashboard. Which command correctly enables recording with the project ID?

A cypress run --dashboard --project your-project-id

B cypress open --record --projectId your-project-id

C cypress run --record --projectId your-project-id

D cypress run --record --key your-project-key

💡 Hint

Recording happens during cypress run and requires the --record flag and --projectId.

To record test runs to the Dashboard, use cypress run --record --projectId your-project-id. The --record flag enables recording, and --projectId identifies the project.

🔧 Debug

advanced

Why does the Dashboard not show recorded test runs after enabling recording?

You enabled recording with cypress run --record --projectId your-project-id, but the Dashboard shows no test runs. What is the most likely cause?

A The <code>projectId</code> is incorrect or does not match the Dashboard project.

B The tests are running in <code>cypress open</code> mode instead of <code>cypress run</code>.

C The <code>--record</code> flag is only for local test runs, not Dashboard.

D The Dashboard service is down and not accepting data.

💡 Hint

Check if the project ID matches exactly what is shown in the Dashboard settings.

If the projectId is wrong, Cypress cannot associate the test run with the Dashboard project, so no data appears.

❓ visualization

advanced

Which Dashboard feature helps identify flaky tests?

On the Cypress Dashboard, which visualization or feature best helps you find tests that sometimes pass and sometimes fail?

A The Test Duration chart showing how long tests take to run.

B The Flaky Tests report showing tests with inconsistent results over time.

C The Screenshots gallery showing images from test failures.

D The Video Playback feature showing full test run videos.

💡 Hint

Look for a report that highlights tests with unstable results.

The Flaky Tests report aggregates tests that fail intermittently, helping teams focus on unstable tests.

❓ data_modeling

expert

How does Cypress Dashboard organize test run data for analysis?

Which data model best describes how Cypress Dashboard stores and relates test run information?

A Test runs contain multiple specs; each spec contains multiple tests; each test can have multiple screenshots and video segments.

B Each test run is a flat list of tests with no grouping by spec or suite.

C Screenshots and videos are stored separately without links to specific tests or runs.

D Test runs are grouped by user sessions, not by specs or tests.

💡 Hint

Think about how tests are grouped logically in a run and how media files relate to tests.

The Dashboard organizes data hierarchically: test runs include specs, specs include tests, and tests link to screenshots and videos for detailed analysis.