Load Data from Test Fixtures in Cypress

Andy Van Slaars
InstructorAndy Van Slaars
Share this video with your friends

Social Share Links

Send Tweet
Published 6 years ago
Updated 5 years ago

When creating integration tests with Cypress, we’ll often want to stub network requests that respond with large datasets. All of this mock data can lead to test code that is hard to read. In this lesson, we’ll see how to use fixtures to keep sample data in files and easily load it on demand in your tests.

Instructor: [00:01] Here we have a test that stubs out a get call to the API/to-dos endpoint and responds with some test data. We'll do this in a lot of our tests, and having all this data scattered around our test will make our test messy after a while.

[00:14] Let's see how we can move this data into a fixture file and use it from there. In the Cypress directory, we have another directory called Fixtures.

[00:21] I'm going to add a new file to that Fixtures directory. I'm going to call it, "todos.json." Now, I'm going to grab that sample data from the test. I'll copy that and paste it into todos.json.

[00:39] Because this is a JSON file, not JavaScript, I'll wrap everything in quotes. With that done, I'll save the file.

[00:48] Now, I'm going to go back to the spec file. I'm going to delete this array. Above our call to cc.rail, I'm going to add a call to cy.fixture. I'm going to pass fixture the name of our JSON file.

[01:05] I'm going to tack a then onto it. Here we're going to get our result. I'll move cy.rail into the then. I'll pass to-dos as the data. I'll save this.

[01:23] We'll double-check that our test is running and everything's working just fine. This has cleaned up our test quite a bit. We've moved all that data out into a fixture file.

[01:34] We can easily re-use it in other spec files. This is such a common setup that we can actually shorten this and make it even cleaner. Rather than calling cy.fixture and then using our then, we can call cy.rail.

[01:50] We can replace this data with a string that uses a fixture prefix followed by the name of our fixture file.

[01:59] Now we're back down to one line. We've cleaned up all the test data. If I save this and switch back to the Cypress runner, we'll see that our test is still running as it was before.

[02:09] Just to verify that this is using our fixture file, let's open our to-dos. We'll update one of the items. We'll save it.

[02:21] We'll re-run our test, and we'll see that that is in fact the data being loaded from our fixture file.

~ 24 minutes ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today