cy.fixture() for loading data in Cypress - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is cy.fixture() used for in Cypress?

cy.fixture() is used to load external fixed data files (like JSON) to use in tests. It helps keep test data separate from test code.

beginner

How do you load a JSON fixture file named user.json in Cypress?

You use cy.fixture('user').then((data) => { ... }) to load the file and access its contents inside the then callback.

intermediate

Why is using cy.fixture() better than hardcoding test data inside tests?

It separates data from code, making tests cleaner and easier to maintain. You can reuse data and update it without changing test logic.

intermediate

Can cy.fixture() load non-JSON files?

Yes, it can load text, CSV, or other file types as strings if you specify the correct encoding or parse them manually.

beginner

How do you use fixture data inside a test to fill a form?

Load the fixture with cy.fixture(), then use the data inside commands like cy.get(...).type(data.field) to fill form fields.

What does cy.fixture('data.json') return?

A A promise with the file content

B A DOM element

C A Cypress command chain

D An error

cy.fixture() returns a Cypress command chain that yields the file content.

Where should fixture files be placed in a Cypress project?

A cypress/support folder

B cypress/fixtures folder

C root folder

D cypress/integration folder

Fixture files belong in the cypress/fixtures folder by default.

How do you access fixture data inside a test?

A Using <code>cy.get()</code>

B Directly calling the file name

C Using <code>cy.visit()</code>

D Using <code>cy.fixture().then()</code>

You use cy.fixture('file').then((data) => { ... }) to access the data.

Which of these is a benefit of using cy.fixture()?

A Separates test data from test code

B Runs tests faster

C Automatically generates test data

D Replaces <code>cy.visit()</code>

Fixtures help keep test data separate from test code for clarity and reuse.

If you want to load a fixture file as plain text, what should you do?

A Pass encoding option to <code>cy.fixture()</code>

B Use <code>cy.readFile()</code> instead

C Rename the file to .txt

D Fixtures only support JSON

You can pass an encoding option like { encoding: 'utf-8' } to load as text.

Explain how to use cy.fixture() to load test data and use it in a Cypress test.

Think about loading JSON files and using their content inside your test steps.

Describe the advantages of using fixtures for test data in Cypress.

Consider how managing data separately helps when tests grow.

Practice

1. What is the primary purpose of cy.fixture() in Cypress testing?

easy

A. To start the Cypress test runner

B. To load external test data files for use in tests

C. To perform assertions on page content

D. To locate elements on the web page

Solution

1. Step 1: Understand the role of cy.fixture()

   cy.fixture() is used to load data from external files like JSON, which can be reused in tests.

2. Step 2: Compare with other Cypress commands

   Locating elements is done by cy.get(), assertions by should(), and starting tests is automatic or via CLI, not cy.fixture().

3. Final Answer:

   To load external test data files for use in tests -> Option B

4. Quick Check:

   Purpose of cy.fixture() = Load test data [OK]

Hint: Remember: fixture means fixed data file loading [OK]

Common Mistakes:

• Confusing cy.fixture() with element selectors
• Thinking it runs tests instead of loading data
• Using it for assertions instead of data loading

2. Which of the following is the correct syntax to load a fixture file named user.json in Cypress?

easy

A. cy.getFixture('user.json').then((data) => { ... })

B. cy.loadFixture('user.json').then((data) => { ... })

C. cy.readFile('user.json').then((data) => { ... })

D. cy.fixture('user.json').then((data) => { ... })

Solution

1. Step 1: Recall the correct Cypress command for fixtures

   The correct command is cy.fixture() to load fixture files.

2. Step 2: Check the syntax for loading and using data

   The syntax uses cy.fixture('filename').then((data) => { ... }) to access the loaded data.

3. Final Answer:

   cy.fixture('user.json').then((data) => { ... }) -> Option D

4. Quick Check:

   Correct fixture syntax = cy.fixture('user.json').then((data) => { ... }) [OK]

Hint: Use cy.fixture('file').then() to load data [OK]

Common Mistakes:

• Using non-existent commands like cy.loadFixture()
• Confusing cy.readFile() with cy.fixture()
• Omitting the .then() callback

3. Given the fixture file user.json contains { "name": "Alice", "age": 30 }, what will the following Cypress code print?

cy.fixture('user.json').then((user) => {
  cy.log(user.name);
  cy.log(user.age);
});

medium

A. Alice and 30

B. user.name and user.age

C. undefined and undefined

D. Error: fixture not found

Solution

1. Step 1: Understand the fixture data structure

   The fixture file contains a JSON object with keys "name" and "age" having values "Alice" and 30 respectively.

2. Step 2: Analyze the Cypress code output

   The code logs user.name and user.age, so it will print "Alice" and 30 in the Cypress log.

3. Final Answer:

   Alice and 30 -> Option A

4. Quick Check:

   Fixture data accessed correctly = Alice, 30 [OK]

Hint: Fixture data keys map to object properties [OK]

Common Mistakes:

• Expecting literal strings instead of values
• Confusing variable names with strings
• Assuming fixture file is missing causing error

4. What is wrong with this Cypress code snippet that tries to load a fixture?

cy.fixture('config').then((data) => {
  cy.log(data.url);
});

Assuming the fixture file is named config.json and is located in the default fixtures folder.

medium

A. There is no error; the code is correct

B. The file extension .json must be included in the fixture name

C. The fixture file must be imported before using cy.fixture()

D. The cy.log command cannot access fixture data

Solution

1. Step 1: Check if file extension is required in cy.fixture()

   Cypress automatically adds .json if omitted, so 'config' works for config.json.

2. Step 2: Verify usage of cy.log() with fixture data

   cy.log() can log any string, including values from fixture data, so this is valid.

3. Final Answer:

   There is no error; the code is correct -> Option A

4. Quick Check:

   Omitting .json is allowed = Code correct [OK]

Hint: Omit .json in fixture name; Cypress adds it automatically [OK]

Common Mistakes:

• Adding .json causes no error but is optional
• Thinking cy.log can't print fixture data
• Trying to import fixture files manually

5. You want to use fixture data to fill a login form in Cypress. The fixture user.json contains { "username": "testuser", "password": "pass123" }. Which code snippet correctly uses cy.fixture() to fill the form fields with IDs #user and #pass?

hard

A. cy.fixture('user').then((data) => { cy.get('#user').type(data.user); cy.get('#pass').type(data.pass); });

B. cy.get('#user').type(user.username); cy.get('#pass').type(user.password); cy.fixture('user');

C. cy.fixture('user').then((user) => { cy.get('#user').type(user.username); cy.get('#pass').type(user.password); });

D. cy.loadFixture('user').then((user) => { cy.get('#user').type(user.username); cy.get('#pass').type(user.password); });

Solution

1. Step 1: Identify correct fixture loading and data usage

   cy.fixture('user').then((user) => { cy.get('#user').type(user.username); cy.get('#pass').type(user.password); }); correctly uses cy.fixture('user').then((user) => { ... }) and accesses user.username and user.password.

2. Step 2: Check form field selectors and typing commands

   It uses cy.get('#user').type() and cy.get('#pass').type() correctly to fill inputs.

3. Final Answer:

   cy.fixture('user').then((user) => { cy.get('#user').type(user.username); cy.get('#pass').type(user.password); }); -> Option C

4. Quick Check:

   Load fixture then fill fields = cy.fixture('user').then((user) => { cy.get('#user').type(user.username); cy.get('#pass').type(user.password); }); [OK]

Hint: Load fixture first, then use data inside .then() callback [OK]

Common Mistakes:

• Using wrong property names like data.user instead of data.username
• Calling cy.fixture() after typing commands
• Using non-existent commands like cy.loadFixture()