GitHub Actions integration in Cypress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the event that triggers the GitHub Actions workflow on push.

Cypress

on: [1]

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

Apull_request

Bschedule

Crelease

Dpush

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pull_request' instead of 'push' when you want to trigger on code push.

Using 'schedule' which runs on a timer, not on code changes.

The push event triggers the workflow when code is pushed to the repository.

2fill in blank

medium

Complete the code to specify the operating system for the job runner.

Cypress

runs-on: [1]

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

Aubuntu-latest

Bwindows-latest

Cmacos-latest

Ddebian-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Windows or macOS when the project expects Linux environment.

Using an unsupported or incorrect OS name.

ubuntu-latest is commonly used for Linux runners in GitHub Actions.

3fill in blank

hard

Fix the error in the step name to correctly run Cypress tests.

Cypress

- name: [1]
  run: npx cypress run

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

ARunCypressTests

BRun Cypress Tests

Crun-cypress-tests

Drun cypress tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or camelCase which is less readable in logs.

Using names without spaces that are hard to read.

Step names should be clear and properly capitalized for readability.

4fill in blank

hard

Fill both blanks to set up Node.js and install dependencies before running tests.

Cypress

- uses: actions/setup-node@v3
  with:
    node-version: [1]
- run: [2]

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

A16

Bnpm install

C18

Dyarn install

Attempts:

3 left

💡 Hint

Common Mistakes

Using a Node.js version not supported by the project.

Running yarn install when the project uses npm.

Node.js version 16 is commonly used, and npm install installs dependencies.

5fill in blank

hard

Fill all three blanks to create a job that runs on Ubuntu, installs dependencies, and runs Cypress tests.

Cypress

jobs:
  test:
    runs-on: [1]
    steps:
      - uses: actions/checkout@v3
      - name: Install dependencies
        run: [2]
      - name: Run Cypress Tests
        run: [3]

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

Aubuntu-latest

Bnpm install

Cnpx cypress run

Dwindows-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using Windows runner when the project expects Linux.

Skipping dependency installation before tests.

Running Cypress tests with wrong commands.

This job runs on Ubuntu, installs dependencies with npm, and runs Cypress tests.

Practice

1. What is the main purpose of integrating Cypress tests with GitHub Actions?

easy

A. To manually trigger tests only when needed

B. To automatically run tests on code changes and catch bugs early

C. To deploy the application to production

D. To write Cypress test scripts inside GitHub

Solution

1. Step 1: Understand GitHub Actions role

   GitHub Actions automates tasks like running tests when code changes.

2. Step 2: Connect Cypress testing purpose

   Cypress tests run automatically to find bugs early without manual effort.

3. Final Answer:

   To automatically run tests on code changes and catch bugs early -> Option B

4. Quick Check:

   Automation of tests = A [OK]

Hint: GitHub Actions automates tasks on code changes [OK]

Common Mistakes:

• Thinking GitHub Actions only deploys code
• Believing tests run manually only
• Confusing test writing with test running

2. Which YAML key is used to specify the event that triggers a GitHub Actions workflow for Cypress tests?

easy

A. jobs

B. run

C. steps

D. on

Solution

1. Step 1: Identify trigger key in GitHub Actions YAML

   The on key defines events like push or pull_request that start the workflow.

2. Step 2: Differentiate from other keys

   run is used inside steps, steps lists commands, jobs groups tasks.

3. Final Answer:

   on -> Option D

4. Quick Check:

   Trigger event key = on [OK]

Hint: Triggers use 'on' key in GitHub Actions YAML [OK]

Common Mistakes:

• Confusing 'run' with trigger event
• Mixing 'steps' with event triggers
• Using 'jobs' as trigger key

3. Given this GitHub Actions snippet, what will happen when code is pushed to the main branch?

on:
  push:
    branches:
      - main
jobs:
  cypress-run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Run Cypress tests
        run: npx cypress run

medium

A. Cypress tests run automatically on push to main branch

B. Tests run only if manually triggered

C. Workflow fails due to missing trigger

D. Tests run on every branch push

Solution

1. Step 1: Analyze trigger event

   The workflow triggers on push to the main branch only.

2. Step 2: Understand job steps

   It checks out code and runs Cypress tests with npx cypress run.

3. Final Answer:

   Cypress tests run automatically on push to main branch -> Option A

4. Quick Check:

   Push to main triggers tests = C [OK]

Hint: Push to main triggers workflow with Cypress run [OK]

Common Mistakes:

• Assuming manual trigger needed
• Thinking tests run on all branches
• Believing workflow lacks trigger

4. You wrote this GitHub Actions workflow but Cypress tests never run:

on:
  push:
    branches:
      - main
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
      - name: Run tests
        run: cypress run

What is the most likely error?

medium

A. Missing 'npx' before 'cypress run' command

B. Wrong branch name under 'push' event

C. Missing 'uses' for Cypress action

D. Incorrect 'runs-on' value

Solution

1. Step 1: Check Cypress run command syntax

   The command should be npx cypress run to run Cypress installed locally.

2. Step 2: Verify other parts

   Branch name 'main' is correct, 'runs-on' is valid, and Cypress action is optional if using CLI.

3. Final Answer:

   Missing 'npx' before 'cypress run' command -> Option A

4. Quick Check:

   Run command needs 'npx' prefix = B [OK]

Hint: Use 'npx cypress run' to execute tests in GitHub Actions [OK]

Common Mistakes:

• Running 'cypress run' without 'npx'
• Changing branch name incorrectly
• Expecting Cypress action is mandatory
• Misconfiguring runner OS

5. You want to run Cypress tests on both push and pull request events but only for the 'develop' branch. Which YAML snippet correctly configures this?

hard

A. on:
push:
branches:
- main
pull_request:
branches:
- main

B. on:
push:
branches:
- main
pull_request:
branches:
- develop

C. on:
push:
branches:
- develop
pull_request:
branches:
- develop

D. on:
push:
branches:
- develop
pull_request:
branches:
- main

Solution

1. Step 1: Identify required events and branches

   Tests must run on both push and pull_request events targeting the 'develop' branch only.

2. Step 2: Match YAML configuration

   on: push: branches: - develop pull_request: branches: - develop correctly lists both events with 'develop' branch under each.

3. Final Answer:

   on: push: branches: - develop pull_request: branches: - develop -> Option C

4. Quick Check:

   Both events on 'develop' branch = D [OK]

Hint: List both events with same branch under 'on' key [OK]

Common Mistakes:

• Mixing branch names between events
• Listing only one event
• Using wrong branch name