Course Introduction: Test Production Ready Apps with Cypress

Brett Cassette
InstructorBrett Cassette
Share this video with your friends

Social Share Links

Send Tweet
Published 5 years ago
Updated 4 years ago

Cypress allows full-stack end-to-end testing. You can test the UI, the frontend stores, the XHR requests, and the database, and interact with every layer in the same test.

But Cypress doesn't do all this out of the box. This course will introduce you to the techniques and abstractions used to handle full-stack testing.

Instructor: [0:00] End-to-end testing gets a bad name. It's flaky. It's unreliable. It's slow. All of that change with Cypress.

[0:10] Cypress sees the world like a real user. It knows what's visible, what's hidden. It automatically waits for objects to show up on the dome. No more sleeps. No more waits. Cypress handles this out-of-the-box.

[0:24] You can travel through time. You can take screenshots. That all just undersell the sales pitch. That says Cypress is better and faster than what came before, but Cypress is more than that. It's a paradigm shift in end-to-end testing. That's because it can test every layer of the stack, the database, the API, the XHR request, our UI, our frontend stores, everything.

[0:56] With Cypress, you can interact with your frontend and your backend and everything in between. Confusing error codes can become a thing of the past because if you test every layer in order, you can pinpoint the exact location where the contract breaks down. You can communicate with new team members more effectively what the dataflow looks like.

[1:17] Yes, we can still use diagrams and drawings, but you can also say it all with the test now. Now you can't quite do all of this out-of-the-box with Cypress. That's why, in this course, I'm going to show you how you can build a transformative testing environment.

egghead
egghead
~ 3 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