Bird
0
0

Your team wants to track flaky tests using Cypress Dashboard. Which combination helps achieve this best?

hard📝 Scenario Q15 of 15
Cypress - CI/CD and Reporting
Your team wants to track flaky tests using Cypress Dashboard. Which combination helps achieve this best?
ARun tests without Dashboard and email reports daily
BRun tests locally and share screenshots manually
CDisable recording and rely on console logs only
DUse <code>--record</code> with project key and enable Dashboard retries
Step-by-Step Solution
Solution:

  1. Step 1: Understand flaky test tracking

    Flaky tests are unstable tests that sometimes fail. Cypress Dashboard can track retries and failures.

  2. Step 2: Identify best practice

    Using --record with the project key sends results to Dashboard, and enabling retries in Dashboard helps track flaky tests.

  3. Final Answer:

    Use --record with project key and enable Dashboard retries -> Option D

  4. Quick Check:

    Track flaky tests = record + retries [OK]
Quick Trick: Record tests and enable retries in Dashboard [OK]
Common Mistakes:
  • Relying on manual screenshots only
  • Disabling recording loses Dashboard benefits
  • Using email reports misses real-time tracking

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Cypress Quizzes
Authentication and Sessions - cy.session() for session caching - Quiz 11easy CI/CD and Reporting - Why CI integration enables continuous testing - Quiz 8hard CI/CD and Reporting - Headless mode - Quiz 7medium CI/CD and Reporting - Parallel execution - Quiz 7medium Component Testing - Props and event testing - Quiz 7medium Component Testing - Mounting Vue components - Quiz 9hard File Operations - cy.readFile() assertions - Quiz 4medium Test Organization and Patterns - Page Object Model in Cypress - Quiz 4medium Test Organization and Patterns - Tagging and filtering tests - Quiz 5medium Test Organization and Patterns - Test configuration per environment - Quiz 3easy