Why CI integration enables continuous testing in Cypress - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run Cypress tests automatically in CI.

Cypress

describe('Login test', () => {
  it('should open login page', () => {
    cy.[1]('https://example.com/login')
  })
})

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

Avisit

Bwait

Ctype

Dclick

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'click' instead of 'visit' to open a page.

The visit command opens a URL in Cypress, which is essential to start a test in CI.

2fill in blank

medium

Complete the code to assert the login button is visible.

Cypress

cy.get('button#login').[1]('be.visible')

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

Ashould

Bclick

Ctype

Dwait

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'click' instead of 'should' for assertions.

The should command asserts that the element meets the condition, here 'be.visible'.

3fill in blank

hard

Fix the error in the CI script to run Cypress tests.

Cypress

steps:
  - name: Run tests
    run: npm [1]

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

Ainstall

Btest

Cbuild

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'npm install' instead of 'npm test' to run tests.

The command npm test runs the test scripts defined in package.json, including Cypress tests in CI.

4fill in blank

hard

Fill both blanks to configure Cypress in GitHub Actions for continuous testing.

Cypress

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Setup Node.js
        uses: actions/setup-node@v2
        with:
          node-version: [1]
      - name: Install dependencies
        run: npm [2]

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

A16

Btest

Cinstall

D14

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'npm test' instead of 'npm install' to install dependencies.

Node.js version 16 is a modern stable version. npm install installs dependencies before running tests in CI.

5fill in blank

hard

Fill all three blanks to write a Cypress test that runs in CI and checks page title.

Cypress

describe('Home page', () => {
  it('has correct title', () => {
    cy.[1]('https://example.com')
    cy.title().[2]('eq', [3])
  })
})

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

Avisit

Bshould

C'Example Domain'

Dclick

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'click' instead of 'visit' to open the page.

Using 'expect' instead of 'should' for assertion.

visit opens the page, should asserts the title equals the expected string 'Example Domain'.

Practice

1. What is the main benefit of integrating Cypress tests with a Continuous Integration (CI) system?

easy

A. Tests require no configuration to run in CI

B. Tests run only when manually triggered by developers

C. Tests run slower but with more detailed logs

D. Tests run automatically on every code change, catching bugs early

Solution

1. Step 1: Understand CI integration purpose

   CI systems automatically run tasks like tests when code changes happen.

2. Step 2: Connect CI with Cypress tests

   Integrating Cypress tests into CI means tests run automatically on each change, catching bugs early.

3. Final Answer:

   Tests run automatically on every code change, catching bugs early -> Option D

4. Quick Check:

   CI auto-runs tests = early bug detection [OK]

Hint: CI runs tests on code changes automatically [OK]

Common Mistakes:

• Thinking tests run only manually in CI
• Assuming CI slows down tests
• Believing no setup is needed for CI

2. Which of the following is the correct way to add Cypress tests to a CI workflow script?

easy

A. Run cypress open in CI to start tests

B. Run npx cypress run command in the CI pipeline

C. Run npm install only, tests run automatically

D. Run npx cypress build to compile tests

Solution

1. Step 1: Identify Cypress command for CI

   The npx cypress run command runs tests in headless mode, suitable for CI.

2. Step 2: Eliminate incorrect commands

   npm install installs packages but doesn't run tests; cypress open opens GUI, not suitable for CI; npx cypress build is invalid.

3. Final Answer:

   Run npx cypress run command in the CI pipeline -> Option B

4. Quick Check:

   Use npx cypress run for CI tests [OK]

Hint: Use npx cypress run to run tests in CI [OK]

Common Mistakes:

• Using cypress open in CI
• Assuming npm install runs tests
• Trying to build Cypress tests

3. Given this CI pipeline snippet:

steps:
  - run: npm install
  - run: npx cypress run
  - run: echo "Tests completed"

What will happen when this pipeline runs after a code push?

medium

A. Tests will not run because npm install is missing

B. Pipeline will fail because npx cypress run is invalid

C. Cypress tests run automatically and results show in the pipeline logs

D. Only the echo command runs, tests are skipped

Solution

1. Step 1: Analyze pipeline commands

   npm install installs dependencies, npx cypress run runs tests, and echo prints a message.

2. Step 2: Understand CI behavior

   After code push, this pipeline runs all steps in order, so tests run automatically and results appear in logs.

3. Final Answer:

   Cypress tests run automatically and results show in the pipeline logs -> Option C

4. Quick Check:

   CI runs install + tests + echo [OK]

Hint: CI runs all steps sequentially including tests [OK]

Common Mistakes:

• Thinking npm install is missing
• Believing npx cypress run is invalid
• Assuming tests are skipped

4. You added Cypress tests to your CI pipeline, but tests never run and the pipeline shows success. What is the most likely cause?

medium

A. The npx cypress run command is missing or misspelled in the pipeline

B. The tests have syntax errors causing them to be skipped

C. The pipeline does not have permission to access the test files

D. The npm install command was run before tests

Solution

1. Step 1: Check pipeline commands for running tests

   If npx cypress run is missing or misspelled, tests won't run but pipeline may still succeed.

2. Step 2: Evaluate other options

   Syntax errors usually cause test failures, not silent skips; permission issues cause errors; npm install before tests is correct practice.

3. Final Answer:

   The npx cypress run command is missing or misspelled in the pipeline -> Option A

4. Quick Check:

   Missing test run command = no tests run [OK]

Hint: Check if npx cypress run is in pipeline script [OK]

Common Mistakes:

• Assuming syntax errors silently skip tests
• Ignoring missing test run command
• Blaming npm install for test skips

5. You want to ensure Cypress tests run on every pull request and report results back to GitHub. Which CI integration feature enables this continuous testing feedback loop?

hard

A. Setting up a GitHub Actions workflow that triggers on pull requests and runs npx cypress run

B. Running Cypress tests only on the main branch after merging

C. Manually running tests locally before pushing code

D. Using cypress open to run tests interactively in CI

Solution

1. Step 1: Identify CI trigger for pull requests

   GitHub Actions can trigger workflows on pull request events to run tests automatically.

2. Step 2: Connect test command and reporting

   Running npx cypress run in this workflow runs tests and reports results back to GitHub, enabling continuous feedback.

3. Final Answer:

   Setting up a GitHub Actions workflow that triggers on pull requests and runs npx cypress run -> Option A

4. Quick Check:

   CI triggers on PR + runs tests = continuous feedback [OK]

Hint: Trigger CI on pull requests to run tests automatically [OK]

Common Mistakes:

• Running tests only after merging
• Relying on manual local test runs
• Using interactive test mode in CI