Starting from open-source projects to enterprise software, most softwares have a huge codebase. Don't believe me? Here is a fact! Some of the Googl...
For further actions, you may consider blocking this person and/or reporting abuse
Worth mentioning that Jest will only test your JavaScript.
But don't rely only on Jest.
A real browser is more than just a JavaScript interpreter.
The best practices mention that you should run automated tests in all major browsers, including Safari (which is used by 20% of users, including myself).
A few weeks ago, I wrote a small article:
What Happens When You Don't Test in Safari
Even using clean vanilla code can lead to major cross-browser issues.
Users can choose the best browser, Safari is becoming the new Internet Explorer, users insist to use it relying on thought about performance/battery and other stuff. Of course performance is important, but new technologies require new behaviors. If you choose Safari you're choosing not to have new technologies. 🤷♂️
That's how democracy works, and I think it's great that users can choose from a number of browsers that are decent.
You have to test in the browsers used by your users, that's why it's important to get that information from your analytics.
Accessibility means making your website work for as many users as possible.
In some cases, that could mean supporting small screen resolutions or certain browsers.
Now, even if we will live in a totalitarian world where Chrome will be the only browser, you'll still have Chrome on Windows and Chrome on Mac.
Ever noticed that the select elements look different on Chrome on Mac vs. Chrome on Windows?
That's just one of the many differences you'll encounter.
Testing on different browsers can be painful, but it's a best practice, there is no workaround.
combine with Playwright to do actions and Jest to assert
Some folks are complaining that Playwright, Puppeteer and others are not following any open standards.
That means there's a risk they might stop working out of the blue with certain browsers or other components.
What will happen then?
You have written a masterpiece, thanks for commenting otherwise I would have missed it. Specially taking Safari as the corner case is genius never actually thought what happens in it.
To be honest the most beginner friendly testing article I have read so far. The way you have explained what is jest and how to do write tests are just amazing. Ultimately, the demo makes it more surreal and useful 😍
Thanks for your time and your comments means a lot 💕
Wow! This made testing so much easier for me. Will definitely try the demo myself🔥
Thanks for your time and your comments means a lot 💕
Very nice document to start with Jest :)
Thanks for your time and your comments means a lot 💕
Great quick intro for beginners getting into Jest 💪
Hearing this for you means a lot. Let me know if this gets a place in your newsletter 😛
Very interesting post
Thanks Jack
A great and useful blog ✨🔥
Got to learn about testing🧪
Thanks for your time and your comments means a lot 💕
Simple and insightful blog ✨ Really liked it
Thanks for your time and your comments means a lot 💕
Love the work
Thanks for your time and your comments means a lot 💕
The article is informative and easy to understand. Keep up the good work!! 🔥
Thanks for your time and your comments means a lot 💕
Every bit of this blog is so insightful, Kudos man. Got to know many things about testing.
Thanks for your time and your comments means a lot 💕
One of the most beginner friendly articles I've come across. Nice work bro 🙌
Thanks for your time and your comments means a lot 💕
Great writing man!! Got to learn few new things!
Keep up the good work 👏🏻
Thanks for your time and your comments means a lot 💕
Nice post :) I learn about testing from this article.
Again very nice article.
Thanks a lot Micky means a lot✨
Thanks chef