JSJ 331: “An Overview of JavaScript Testing in 2018” with Vitali Zaidman

JavaScript Jabber - A podcast by Charles M Wood - Tuesdays

Panel: - https://twitter.com/coolaj86?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- http://www.aimeemarieknight.com- https://twitter.com/josepheames?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- https://twitter.com/cmaxw?lang=en Special Guests: https://medium.com/@vzaidman In this episode, the panel talks with programmer, https://medium.com/@vzaidman, who is working with Software Solutions Company. He researches technologies and starts new projects all the time, and looks at these new technologies within the market. The panel talks about testing JavaScript in 2018 and https://jestjs.io.Show Topics:1:32 – Chuck: Let’s talk about testing JavaScript in 2018.1:53 – https://medium.com/@vzaidman talks about solving problems in JavaScript.2:46 – Chuck asks https://medium.com/@vzaidman a question.3:03 – Vitali’s answer.3:30 – Why https://jestjs.io? Why not Mocha or these other programs?3:49 – https://jestjs.io is the best interruption of what testing should look like and the best practice nowadays. There are different options, they can be better, but https://jestjs.io has this great support from their community. There are great new features.4:31 – Chuck to Joe: What are you using for testing nowadays?4:43 – Joe: I use Angular, primarily.6:01 – Like life, it’s sometimes easier to use things that make things very valuable.7:55 – Aimee: I have heard great things about http://www.cypress.com/documentation/software-and-drivers/free-and-open-source-software-download-page, but at work we are using another program.8:22 – Vitali: Check out my article.8:51 – Aimee: There are too many problems with the program that we use at work.9:39 – Panelist to Vitali: I read your article, and I am a fan. Why do you pick Test Café over Cypress, and how familiar are you with Cypress? What about Selenium and other programs?10:12 – Vitali: “Test Café and Cypress are competing head-to-head.”Listen to Vitali’s suggestions and comments per the panelists’ question at this timestamp.11:25 – Chuck: I see that you use sign-on...12:29 – Aimee: Can you talk abouthttps://github.com/GoogleChrome/puppeteer? It seems promising.12:45 – Vitali: Yes, Puppeteer is promising. It’s developed by Google and by Chrome. You don’t want to use all of your tests in Puppeteer, because it will be really hard to do in other browsers.13:26: Panelist: “...5, 6, 7, years ago it was important of any kind of https://www.javascript.com testing you had no idea if it worked in one browser and it not necessarily works in another browser. That was 10 years ago. Is multiple browsers testing as important then as it is now?14:51: Vitali answers the above question.15:30 – Aimee: If it is more https://www.javascript.com heavy then it could possibly cause more problems.15:56 – Panelist: I agree with this.16:02 – Vitali continues this conversation with additional comments.16:17...