Cypress folder structure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the cypress/e2e folder?

The cypress/e2e folder holds all the end-to-end test files. These tests simulate user actions in the browser to check if the app works as expected.

beginner

What kind of files do you put in the cypress/support folder?

The cypress/support folder contains helper files like commands and setup code that run before tests. It helps keep tests clean and reusable.

beginner

Why is the cypress/fixtures folder important?

The cypress/fixtures folder stores sample data files (like JSON) used in tests. This data helps tests run with consistent inputs.

intermediate

What does the cypress/plugins folder do?

The cypress/plugins folder contains code to extend Cypress’s behavior, like modifying how tests run or adding custom tasks.

beginner

How does organizing tests in the Cypress folder structure help your testing?

Organizing tests and support files in the right folders makes your project easy to understand and maintain. It helps you find tests, reuse code, and run tests smoothly.

Which folder in Cypress holds your test scripts?

A cypress/fixtures

B cypress/e2e

C cypress/support

D cypress/plugins

The cypress/e2e folder is where you write your test scripts that simulate user actions.

Where do you put reusable commands and setup code in Cypress?

A cypress/support

B cypress/plugins

C cypress/fixtures

D cypress/e2e

The cypress/support folder is for reusable commands and setup code that runs before tests.

What type of files are stored in cypress/fixtures?

A Sample data files

B Helper functions

C Test scripts

D Plugin code

The cypress/fixtures folder stores sample data files like JSON used in tests.

Which folder would you use to add custom tasks or extend Cypress features?

A cypress/e2e

B cypress/support

C cypress/fixtures

D cypress/plugins

The cypress/plugins folder is for code that extends Cypress’s behavior or adds custom tasks.

Why is it important to keep tests and support files organized in Cypress?

A To make tests run slower

B To confuse team members

C To make the project easy to maintain and understand

D To avoid writing tests

Organizing files properly helps keep the project easy to maintain and understand.

Describe the main folders in the Cypress folder structure and their purposes.

Think about where you write tests, store data, add helpers, and customize Cypress.

Explain how organizing your Cypress project folders helps improve your testing workflow.

Consider how good organization helps teamwork and saves time.

Practice

1. Which folder in Cypress is primarily used to store your test files?

easy

A. plugins

B. fixtures

C. support

D. e2e

Solution

1. Step 1: Understand folder purposes

   The e2e folder is designed to hold end-to-end test files in Cypress.

2. Step 2: Differentiate from other folders

   fixtures holds test data, support has helper code, and plugins manages plugins, not tests.

3. Final Answer:

   e2e -> Option D

4. Quick Check:

   Tests go in e2e folder [OK]

Hint: Tests live in e2e folder by default [OK]

Common Mistakes:

• Confusing fixtures with test files
• Thinking support holds tests
• Assuming plugins stores tests

2. Which of the following is the correct path to place fixture files in a Cypress project?

easy

A. cypress/fixtures

B. cypress/support/fixtures

C. cypress/e2e/fixtures

D. fixtures/cypress

Solution

1. Step 1: Recall default Cypress folder structure

   Fixture files are stored directly inside the cypress/fixtures folder.

2. Step 2: Eliminate incorrect paths

   Options placing fixtures inside support or e2e are incorrect. Also, fixtures/cypress is not standard.

3. Final Answer:

   cypress/fixtures -> Option A

4. Quick Check:

   Fixtures folder is cypress/fixtures [OK]

Hint: Fixtures go directly under cypress/fixtures [OK]

Common Mistakes:

• Placing fixtures inside support
• Adding extra nested folders incorrectly
• Confusing fixtures with test files location

3. Given the following folder structure, where will Cypress look for support files by default?

cypress/
  e2e/
  fixtures/
  support/
    commands.js
    index.js

medium

A. cypress/support/commands.js

B. cypress/support/index.js

C. cypress/fixtures/index.js

D. cypress/e2e/index.js

Solution

1. Step 1: Identify default support file

   Cypress automatically loads cypress/support/index.js as the support file.

2. Step 2: Differentiate from other files

   commands.js is imported inside index.js, but Cypress looks for index.js by default.

3. Final Answer:

   cypress/support/index.js -> Option B

4. Quick Check:

   Support file = cypress/support/index.js [OK]

Hint: Support file is always support/index.js by default [OK]

Common Mistakes:

• Choosing commands.js as main support file
• Looking in e2e or fixtures folders for support
• Assuming support file is optional

4. You placed your test files inside cypress/support instead of cypress/e2e. What issue will you face?

medium

A. Tests will not run because Cypress does not look for tests in support

B. Tests will run normally without any issue

C. Tests will run but fixtures won't load

D. Support commands will override test files

Solution

1. Step 1: Understand folder roles

   The support folder is for helper code, not test files.

2. Step 2: Consequence of wrong placement

   Cypress only runs tests inside e2e folder by default, so tests in support won't run.

3. Final Answer:

   Tests will not run because Cypress does not look for tests in support -> Option A

4. Quick Check:

   Tests must be in e2e, not support [OK]

Hint: Tests outside e2e folder won't run [OK]

Common Mistakes:

• Assuming tests run anywhere inside cypress folder
• Confusing support folder as test location
• Thinking fixtures affect test execution location

5. You want to organize your test data for multiple environments in Cypress. Which folder and structure is best practice to keep environment-specific fixture files?

hard

A. Store environment data inside cypress/e2e alongside tests

B. Put environment files inside cypress/support as separate JS files

C. Place all environment files inside cypress/fixtures with subfolders like dev, prod

D. Create a new folder outside cypress for environment data

Solution

1. Step 1: Identify fixture folder purpose

   The cypress/fixtures folder is meant for test data files, including environment-specific data.

2. Step 2: Organize environment data properly

   Using subfolders like dev and prod inside fixtures keeps data organized and easy to load.

3. Final Answer:

   Place all environment files inside cypress/fixtures with subfolders like dev, prod -> Option C

4. Quick Check:

   Environment data belongs in fixtures with subfolders [OK]

Hint: Use subfolders in fixtures for environment data [OK]

Common Mistakes:

• Putting data in support folder
• Mixing data files with test files in e2e
• Creating folders outside Cypress structure