Fronnta check: advantages, disadvantages and instability

The author, Noam Rosenthal, is shared by the experience of organizing the test and finding the right balance between the front and subsystems, as well as between different strategies: unite testing, integration testing and E2E testing. He talks about the difficulties that developers are faced when organizing the testing of their components of UI.

🚀 Rosenthal explains that units of tests often do not detect "interesting" things that happen to users and systems, and E2E tests usually take a long time or require complex configuration. He also notes that developers often face a lot of tools (Jest, Cypress, Playwright and others), and it is difficult for them to choose which one to use.

💡 The author states that testing is not just about tools and processes. It's about architecture. He notes that we, as a rule, do not create our fronttan as a system, but rather as a set of components and functions that make up user stories.

🧠 Own considerations: The importance of proper testing can not be overestimated. Developers should be aware that testing is an integral part of the development process, not just an additional task that needs to be accomplished. However, choosing the right balance between different types of tests can be complicated, and experience can be indispensable here.

• 📌 Testing is not only about tools and processes, but also about architecture.
• 📌 The correct balance between units, integration testing and E2E testing is important for an effective testing system.
• 📌 Units and E2E tests have their advantages and disadvantages, and should be used with caution.