![]() That's true because e2e tests have become easier (but not dead easy) to write and to repeat. ![]() I also read an interesting article saying (cannot find it anymore) " the js community has finally realized that web apps must be E2E tested first, instead of unit tested ". The ubiquity of the web (progressive web apps, or React Native-like projects, made possible to use js on mobile too).popular UI frameworks (react, vue, angular.) were designed from the ground up to be testable. ![]() testing in JS became a necessity!Īt the start of 2019 there was a lot of hype around Javascript testing, mainly because of: The language itself is evolving every year, after the first 20 years of no interesting additions. Javascript ecosystem is growing exponentially with thousands of packages, frameworks, ideas, applications that come out all the time. Unfortunately all our testing efforts were only directed towards the backend, probably because of the language this means that we could not find UI bugs before it was too late.įast fotward many years, GWT is not a thing anymore (good for you!), and Javascript is one of the most studied and used languages of the world. At the time (2012) the backend was written in Java and the frontend was written in GWT, a Java framework to build UIs that is compiled to JS. When I started my career as a software developer I immediately become "friend" with the concepts of unit testing and integration testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |