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

## Cost 

- As the complexity of the project increases, we add more tools to the existing toolchain. If a testing culture is not upheld , then  problems can arise.

- In your first approach, testing can add more cons than pros; you might end up maintaining more tests than you code.

- Tests can give you false confidence, and you might blame them when a bug goes online.


- Testing requires a mind shift.

- Learning to test takes time. While it will have you develop applications more quickly in the long term. During the learning process, the experience will make you faster and faster but, in the beginning, you cannot avoid the learning curve.

- Testing must be treated as an essential part of an application’s final product.

- Testing might feel like yet another app that must be maintained. 


Testing might be frustrating to learn, but don’t be afraid to take breaks, ask for help, and most importantly, don’t give up!

# Cost 

- As the complexity of the project increases, we add more tools to the existing toolchain. If a testing culture is not upheld , then  problems can arise.

- In your first approach, testing can add more cons than pros; you might end up maintaining more tests than you code.

- Tests can give you false confidence, and you might blame them when a bug goes online.


- Testing requires a mind shift.

- Learning to test takes time. While it will have you develop applications more quickly in the long term. During the learning process, the experience will make you faster and faster but, in the beginning, you cannot avoid the learning curve.

- Testing must be treated as an essential part of an application’s final product.

- Testing might feel like yet another app that must be maintained. 


Testing might be frustrating to learn, but don’t be afraid to take breaks, ask for help, and most importantly, don’t give up!

Cost of Testing

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

Cost of Testing

Cost