Why CI integration enables continuous testing in Cypress - Automation Benefits in Action

Verify that tests run automatically on CI after code push

Preconditions (2)

Step 1: Push a new commit to the main branch of the repository

Step 2: Observe the CI pipeline starting automatically

Step 3: Wait for the Cypress tests to run in the CI environment

Step 4: Check the CI test report for pass/fail status

✅ Expected Result: The CI pipeline triggers automatically on push, Cypress tests run, and the test report shows all tests passing

Automation Requirements - Cypress

Assertions Needed:

Verify that the test suite runs without failures

Verify that the test report is generated

Verify that the CI environment variables are accessible

Best Practices:

Use Cypress commands and assertions consistently

Use environment variables for CI-specific configurations

Avoid hardcoded waits; use Cypress built-in retries and waits

Structure tests for easy CI integration

Automated Solution

Cypress

/// <reference types="cypress" />

describe('CI Integration Continuous Testing', () => {
  it('should run tests successfully in CI environment', () => {
    // Check if running in CI by environment variable
    const isCI = Cypress.env('CI') === 'true';
    expect(isCI).to.be.true;

    // Visit a sample page (replace with actual app URL or test page)
    cy.visit('https://example.cypress.io');

    // Verify page contains expected content
    cy.contains('Kitchen Sink').should('be.visible');

    // Additional test steps can be added here
  });
});

This Cypress test checks if it is running in a CI environment by reading the CI environment variable, which is commonly set by CI providers. It asserts that this variable is true to confirm the test runs in CI.

Then it visits a sample page and verifies visible content to ensure the test executes properly.

This structure ensures the test can run both locally and in CI, but the assertion on CI variable confirms the continuous testing environment.

Using Cypress environment variables and built-in commands avoids flaky tests and supports smooth CI integration.

Common Mistakes - 3 Pitfalls

Hardcoding URLs or credentials in tests

Using fixed waits like cy.wait(5000)

Not checking if tests run in CI environment

Bonus Challenge

Now add data-driven testing with 3 different environment variable settings for CI and non-CI runs

Show Hint