Delve into front-end testing principles, learn best practices for writing enduring tests, and discover strategies for E2E testing and integration into CI pipelines. Gain actionable testing insights.

React Testing 101 Component, Integration, and End-to-end Testing_1.png

tarball.tar.gz

jest

jest_describe

jest_onlytest

skiptest

aftereach

headless

foo2

opening

first_test

custom

final_job

foo_final

This course will provide you with important information, principles, and experience-based advice, to enter the world of testing methodologies. 

Here, you will learn the best practices to follow to write useful and lasting tests, how to test different user flows without a working back-end, how to write effective end-to-end tests (E2E), and how to integrate tests into development and Continuous Integration pipelines.

At the end of the course, you will be able to apply the fundamental principles of the test methodologies to understand what and how to test effectively.

Front-end Testing 101: Integration and End-to-end Testing

The only difference is that the headless browser doesn't have a UI.

The headless browser can't be used for testing.

Headless browsers take more time than a standard browser to load CSS, JavaScript, and open and render HTML DOM. 

What differentiates a standard browser from a headless one?

What differentiates a standard browser from a headless one?

Yes, because E2E tests are fast and can save time.

Apart from rare cases, no. E2E tests aren't practical because they aren't reliable neither fast.

Yes, because they are simple and reliable.

Can I have a test suite composed just of E2E tests?

Can I have a test suite composed just of E2E tests?

Yes, because E2E testing doesn't need a backend.

No, an E2E test needs a working back-end.

Could you write an E2E test if the back-end isn't ready or not fully working yet?

Could you write an E2E test if the back-end isn’t ready or not fully working yet?

If we need to visually see the test runs.

For all the contexts where a UI isn't needed like a Continuous Integration environment.

If a headless browser doesn't show its UI, what is it useful for?

If a headless browser doesn’t show its UI, what is it useful for?

The back-end is not on my local machine, can I write and launch with E2E tests on my machine if I don't have a reliable connection?

The back-end is not on my local machine, can I write and launch with E2E tests on my machine if I don’t have a reliable connection?

Let's test your understanding of the concepts covered so far.

Introduction

E2E Testing

The First E2E Test

Polishing the E2E test

Ajax Requests

Custom Commands

UI Integration Tests

Other Best Practices

Bonus Section

Conclusion

Appendix

Quiz on E2E Testing