Podcasts about javascript testing

In today's episode, I talk about testing vanilla JavaScript.In today's episode, I talk about testing vanilla JavaScript.Show Notes & Transcript →

In today's episode, I talk about testing vanilla JavaScript. Links Testing Vanilla JS Course & Book Martin Fowler on the history of integration tests Justin Searls on the point of testing

Dave is pondering Ariana Grande's voice, should you use a SSG for custom landing pages or WordPress, Chris digs apps that allow menu customization, thoughts on companies getting acquired, where should you start with JavaScript testing, is there CMS tools in JavaScript land, and why choose Remix over Rails / Laravel today?

Testing JavaScript Applications by Lucas da Costa (Coupon for 40% off: podjsjabber19) Lucas da Costa literally wrote the book on testing JavaScript. He's also maintainer on ChaiJS and Sinon. The podcast follows a three part structure for testing: Entrance tests, integration tests, and structural tests. These form a pyramid of testing that has the entrance tests at the base and the structural and system tests at the top. The episode also covers TDD and approaches to different kinds of JavaScript testing. Panel AJ O’Neal Aimee Knight Steve Edwards Guest Lucas da Costa Sponsors Audible.com Raygun | Click here to get started on your free 14-day trial Links Testing JavaScript Applications book Lucas' Website Lucas' Terminal Guide Why Flat Earthers are Bad at QA Picks Lucas - HiDPI (Retina) on any display Lucas - RDM: Lucas - Quartz Debug (XCode Additional Tools) Aimee - Vanilla-todo AJ - iTerm2 AJ - Fish Shell AJ - Cloud Encabulator link Steve - https://www.youtube.com/watch?v=BRupqYXNUVw Lucas - The Sense of Style by Steven Pinker (Audiobook) Lucas - On Writing Well Lucas - Actionable Agile Metrics For Predictability: An Introduction Lucas - https://github.com/neovim/neovim Testing JavaScript Applications by Lucas da Costa (Coupon for 40% off: podjsjabber19) 

Testing JavaScript Applications by Lucas da Costa (Coupon for 40% off: podjsjabber19) Lucas da Costa literally wrote the book on testing JavaScript. He's also maintainer on ChaiJS and Sinon. The podcast follows a three part structure for testing: Entrance tests, integration tests, and structural tests. These form a pyramid of testing that has the entrance tests at the base and the structural and system tests at the top. The episode also covers TDD and approaches to different kinds of JavaScript testing. Panel AJ O’Neal Aimee Knight Steve Edwards Guest Lucas da Costa Sponsors Audible.com Raygun | Click here to get started on your free 14-day trial Links Testing JavaScript Applications book Lucas' Website Lucas' Terminal Guide Why Flat Earthers are Bad at QA Picks Lucas - HiDPI (Retina) on any display Lucas - RDM: Lucas - Quartz Debug (XCode Additional Tools) Aimee - Vanilla-todo AJ - iTerm2 AJ - Fish Shell AJ - Cloud Encabulator link Steve - https://www.youtube.com/watch?v=BRupqYXNUVw Lucas - The Sense of Style by Steven Pinker (Audiobook) Lucas - On Writing Well Lucas - Actionable Agile Metrics For Predictability: An Introduction Lucas - https://github.com/neovim/neovim Testing JavaScript Applications by Lucas da Costa (Coupon for 40% off: podjsjabber19) 

Testing JavaScript Applications by Lucas da Costa (Coupon for 40% off: podjsjabber19) Lucas da Costa literally wrote the book on testing JavaScript. He's also maintainer on ChaiJS and Sinon. The podcast follows a three part structure for testing: Entrance tests, integration tests, and structural tests. These form a pyramid of testing that has the entrance tests at the base and the structural and system tests at the top. The episode also covers TDD and approaches to different kinds of JavaScript testing. Panel AJ O’Neal Aimee Knight Steve Edwards Guest Lucas da Costa Sponsors Audible.com Raygun | Click here to get started on your free 14-day trial Links Testing JavaScript Applications book Lucas' Website Lucas' Terminal Guide Why Flat Earthers are Bad at QA Picks Lucas - HiDPI (Retina) on any display Lucas - RDM: Lucas - Quartz Debug (XCode Additional Tools) Aimee - Vanilla-todo AJ - iTerm2 AJ - Fish Shell AJ - Cloud Encabulator link Steve - https://www.youtube.com/watch?v=BRupqYXNUVw Lucas - The Sense of Style by Steven Pinker (Audiobook) Lucas - On Writing Well Lucas - Actionable Agile Metrics For Predictability: An Introduction Lucas - https://github.com/neovim/neovim Testing JavaScript Applications by Lucas da Costa (Coupon for 40% off: podjsjabber19) 

The one when Si talks to Marc about classic coding, fighting sepsis and leading teams in tech.

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus Clubhouse CacheFly Host: Charles Max Wood Guest: Vitali Zaidman Episode Summary In this episode of My JavaScript Story, Charles hosts Vitali Zaidman, Technical Lead at WellDone Software Solutions. He is also the author of the popular blog piece: “An Overview of JavaScript Testing in 2019”. Vitali has been writing code since he was 13 years old. After completing his military service, he attended The Open University of Israel where he took computer science courses. He picked JavaScript not knowing that it was going to be so popular. He has been working for WellDone Software Solutions since he was a student where he has had the chance to work in many different projects. Vitali feels in order to keep up with technology it is important to work in different projects. Vitali talks about projects he has worked on that he is proud of, one of which is his library at https://github.com/welldone-software/why-did-you-render Links JSJ 331: An Overview of JavaScript Testing in 2018 with Vitali Zaidman https://www.facebook.com/vzaidman https://twitter.com/vzaidman https://github.com/vzaidman https://medium.com/@vzaidman https://bitsrc.io/vzaidman https://www.welldone-software.com/ https://www.powtoon.com/home/? Picks Vitali Zaidman: https://www.testim.io/ https://applitools.com/ An Overview of JavaScript Testing in 2019 by Vitali Zaidman https://github.com/welldone-software/why-did-you-render Charles Max Wood: https://www.vrbo.com/ https://paradehomes.com/web/ https://www.tripit.com/web Player's Handbook Dungeons & Dragons Core Rule Book

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus Clubhouse CacheFly Host: Charles Max Wood Guest: Vitali Zaidman Episode Summary In this episode of My JavaScript Story, Charles hosts Vitali Zaidman, Technical Lead at WellDone Software Solutions. He is also the author of the popular blog piece: “An Overview of JavaScript Testing in 2019”. Vitali has been writing code since he was 13 years old. After completing his military service, he attended The Open University of Israel where he took computer science courses. He picked JavaScript not knowing that it was going to be so popular. He has been working for WellDone Software Solutions since he was a student where he has had the chance to work in many different projects. Vitali feels in order to keep up with technology it is important to work in different projects. Vitali talks about projects he has worked on that he is proud of, one of which is his library at https://github.com/welldone-software/why-did-you-render Links JSJ 331: An Overview of JavaScript Testing in 2018 with Vitali Zaidman https://www.facebook.com/vzaidman https://twitter.com/vzaidman https://github.com/vzaidman https://medium.com/@vzaidman https://bitsrc.io/vzaidman https://www.welldone-software.com/ https://www.powtoon.com/home/? Picks Vitali Zaidman: https://www.testim.io/ https://applitools.com/ An Overview of JavaScript Testing in 2019 by Vitali Zaidman https://github.com/welldone-software/why-did-you-render Charles Max Wood: https://www.vrbo.com/ https://paradehomes.com/web/ https://www.tripit.com/web Player's Handbook Dungeons & Dragons Core Rule Book

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus Clubhouse CacheFly Host: Charles Max Wood Guest: Vitali Zaidman Episode Summary In this episode of My JavaScript Story, Charles hosts Vitali Zaidman, Technical Lead at WellDone Software Solutions. He is also the author of the popular blog piece: “An Overview of JavaScript Testing in 2019”. Vitali has been writing code since he was 13 years old. After completing his military service, he attended The Open University of Israel where he took computer science courses. He picked JavaScript not knowing that it was going to be so popular. He has been working for WellDone Software Solutions since he was a student where he has had the chance to work in many different projects. Vitali feels in order to keep up with technology it is important to work in different projects. Vitali talks about projects he has worked on that he is proud of, one of which is his library at https://github.com/welldone-software/why-did-you-render Links JSJ 331: An Overview of JavaScript Testing in 2018 with Vitali Zaidman https://www.facebook.com/vzaidman https://twitter.com/vzaidman https://github.com/vzaidman https://medium.com/@vzaidman https://bitsrc.io/vzaidman https://www.welldone-software.com/ https://www.powtoon.com/home/? Picks Vitali Zaidman: https://www.testim.io/ https://applitools.com/ An Overview of JavaScript Testing in 2019 by Vitali Zaidman https://github.com/welldone-software/why-did-you-render Charles Max Wood: https://www.vrbo.com/ https://paradehomes.com/web/ https://www.tripit.com/web Player's Handbook Dungeons & Dragons Core Rule Book

Panel: AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guests: Vitali Zaidman In this episode, the panel talks with programmer, Vitali Zaidman, 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 Jest. Show Topics: 1:32 – Chuck: Let’s talk about testing JavaScript in 2018. 1:53 – Vitali talks about solving problems in JavaScript. 2:46 – Chuck asks Vitali a question. 3:03 – Vitali’s answer. 3:30 – Why Jest? Why not Mocha or these other programs? 3:49 – Jest is the best interruption of what testing should look like and the best practice nowadays. There are different options, they can be better, but Jest 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 Cypress, 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 about 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 JavaScript 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 JavaScript 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 – Aimee: “I see that Safari is the new Internet Explorer.” 16:23: Chuck: “Yes, you have to know your audience. Are they using older browsers? What is the compatibility?” 17:01 – Vitali: There are issues with the security. Firefox has a feature of tracking protection; something like that. 17:33 – Question to Vitali by Panelist. 17:55 – Vitali answers the question. 18:30 – Panelist makes additional comments. 18:43 – If you use Safari, you reap what you sow. 18:49 – Chuck: I use Chrome on my iPhone. (Aimee does, too.) Sometimes I wind up in Safari by accident. 19:38 – Panelist makes comments. 19:52 – Vitali tells a funny story that relates to this topic. 20:45 – There are too many standards out there. 21:05 – Aimee makes comments. 21:08 – Brutalist Web Design. Some guy has this site – Brutalist Web Design – where he says use basic stuff and stop being so custom. Stop using the web as some crazy platform, and if your site is a website that can be scrolled through, that’s great. It needs to be just enough for people to see your content. 22:16 – Aimee makes additional comments about this topic of Brutalist Web Design. 22:35 – Panelist: I like it when people go out and say things like that. 22:45 – Here is the point, though. There is a difference between a website and a web application. Really the purpose is to read an article. 23:37 – Vitali chimes in. 24:01 – Back to the topic of content on websites. 25:17 – Panelist: Medium is very minimal. Medium doesn’t feel like an application. 26:10 – Is the website easy enough for the user to scroll through and get the content like they want to? 26:19 – Advertisement. 27:22 – See how far off the topic we got? 27:31 – These are my favorite conversations to have. 27:39 – Vitali: Let’s talk about how my article got so popular. It’s an interesting thing, I started researching “testing” for my company. We wanted to implement one of the testing tools. Instead of creating a presentation, I would write first about it in Medium to get feedback from the community as well. It was a great decision, because I got a lot of comments back. I enjoyed the experience, too. Just write about your problem in Medium to see what people say. 28:48 – Panelist: You put a ton of time and energy in this article. There are tons of links. Did you really go through all of those articles? 29:10 – Yes, what are the most permanent tools? I was just reading through a lot of comments and feedback from people. I tested the tools myself, too! 29:37 – Panelist: You broke down the article, and it’s a 22-minute read. 30:09 – Vitali: I wrote the article for my company, and they ad to read it. 30:24 – Panelist: Spending so much time – you probably felt like it was apart of your job. 30:39 – Vitali: I really like creating and writing. It was rally amazing for me and a great experience. I feel like I am talented in this area because I write well and fast. I wanted to express myself. 31:17 – Did you edit and review? 31:23 – Vitali: I wrote it by myself and some friends read it. There were serious mistakes, and that’s okay I am not afraid of mistakes. This way you get feedback. 32:10 – Chuck: “Some people see testing in JavaScript, and people look at this and say there are so much here. Is there a place where people can start, so that way they don’t’ get too overwhelmed? Is there a way to ease into this and take a bite-size at a time?” 32:52 – Vitali: “Find something that works for them. Read the article and start writing code.” He continues this conversation from here on out. 34:03 – Chuck continues to ask questions and add other comments. 34:16 – Vitali chimes-in.  34:38 – Chuck.  34:46 – Vitali piggybacks off of Chuck’s comments. 36:14 – Panelist: Let’s go back to Jest. There is a very common occurrence where we see lots of turn and we see ideas like this has become the dominant or the standard, a lot of people talk about stuff within this community. Then we get this idea that ‘this is the only thing that is happening.’ Transition to jQuery to React to... With that context do you feel like Jest will be a dominant program? Are we going to see Jest used just as common as Mocha and other popular programs? 38:15 – Vitali comments on the panelist’s question. 38:50 – Panelist: New features. Are the features in Jest (over Jasmine, Mocha, etc.) so important that it will drive people to it by itself? 40:30 – Vitali comments on this great question. 40:58 – Panelist asks questions about features about Jest. 41:29 – Vitali talks about this topic. 42:14 – Let’s go to picks! 42:14 – Advertisement. Links: Vitali Zaidman’s Facebook Vitali Zaidman’s Medium Vitali Zaidman’s GitHub Vitali Zaidman’s NPM Vitali Zaidman’s LinkedIn Vitali Zaidman’s Medium Article JavaScript Brutalist Web Design Jasmine Cypress React jQuery Jest Protractor – end to end testing for Angular Test Café Intern Sinon XKCD Sponsors: Kendo UI Sentry Digital Ocean Cache Fly Picks: AJ O’Neal Continuous from last week’s episode: Crossing the Chasm – New Technologies from Niche to General Adaptation. Go Lang Joe Eames Board Game: Rajas of the Ganges Framework Summit Conference in Utah React Conference Aimee Knight Hacker News – “Does Software Understand Complexity” via Michael Feathers Cream City Code Chuck E-Book: How do I get a job? Express VPN Vitali Book: The Square and The Tower: Networks and Power, from the Freemasons to Facebook by Niall Ferguson My article!

Panel: AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guests: Vitali Zaidman In this episode, the panel talks with programmer, Vitali Zaidman, 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 Jest. Show Topics: 1:32 – Chuck: Let’s talk about testing JavaScript in 2018. 1:53 – Vitali talks about solving problems in JavaScript. 2:46 – Chuck asks Vitali a question. 3:03 – Vitali’s answer. 3:30 – Why Jest? Why not Mocha or these other programs? 3:49 – Jest is the best interruption of what testing should look like and the best practice nowadays. There are different options, they can be better, but Jest 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 Cypress, 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 about 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 JavaScript 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 JavaScript 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 – Aimee: “I see that Safari is the new Internet Explorer.” 16:23: Chuck: “Yes, you have to know your audience. Are they using older browsers? What is the compatibility?” 17:01 – Vitali: There are issues with the security. Firefox has a feature of tracking protection; something like that. 17:33 – Question to Vitali by Panelist. 17:55 – Vitali answers the question. 18:30 – Panelist makes additional comments. 18:43 – If you use Safari, you reap what you sow. 18:49 – Chuck: I use Chrome on my iPhone. (Aimee does, too.) Sometimes I wind up in Safari by accident. 19:38 – Panelist makes comments. 19:52 – Vitali tells a funny story that relates to this topic. 20:45 – There are too many standards out there. 21:05 – Aimee makes comments. 21:08 – Brutalist Web Design. Some guy has this site – Brutalist Web Design – where he says use basic stuff and stop being so custom. Stop using the web as some crazy platform, and if your site is a website that can be scrolled through, that’s great. It needs to be just enough for people to see your content. 22:16 – Aimee makes additional comments about this topic of Brutalist Web Design. 22:35 – Panelist: I like it when people go out and say things like that. 22:45 – Here is the point, though. There is a difference between a website and a web application. Really the purpose is to read an article. 23:37 – Vitali chimes in. 24:01 – Back to the topic of content on websites. 25:17 – Panelist: Medium is very minimal. Medium doesn’t feel like an application. 26:10 – Is the website easy enough for the user to scroll through and get the content like they want to? 26:19 – Advertisement. 27:22 – See how far off the topic we got? 27:31 – These are my favorite conversations to have. 27:39 – Vitali: Let’s talk about how my article got so popular. It’s an interesting thing, I started researching “testing” for my company. We wanted to implement one of the testing tools. Instead of creating a presentation, I would write first about it in Medium to get feedback from the community as well. It was a great decision, because I got a lot of comments back. I enjoyed the experience, too. Just write about your problem in Medium to see what people say. 28:48 – Panelist: You put a ton of time and energy in this article. There are tons of links. Did you really go through all of those articles? 29:10 – Yes, what are the most permanent tools? I was just reading through a lot of comments and feedback from people. I tested the tools myself, too! 29:37 – Panelist: You broke down the article, and it’s a 22-minute read. 30:09 – Vitali: I wrote the article for my company, and they ad to read it. 30:24 – Panelist: Spending so much time – you probably felt like it was apart of your job. 30:39 – Vitali: I really like creating and writing. It was rally amazing for me and a great experience. I feel like I am talented in this area because I write well and fast. I wanted to express myself. 31:17 – Did you edit and review? 31:23 – Vitali: I wrote it by myself and some friends read it. There were serious mistakes, and that’s okay I am not afraid of mistakes. This way you get feedback. 32:10 – Chuck: “Some people see testing in JavaScript, and people look at this and say there are so much here. Is there a place where people can start, so that way they don’t’ get too overwhelmed? Is there a way to ease into this and take a bite-size at a time?” 32:52 – Vitali: “Find something that works for them. Read the article and start writing code.” He continues this conversation from here on out. 34:03 – Chuck continues to ask questions and add other comments. 34:16 – Vitali chimes-in.  34:38 – Chuck.  34:46 – Vitali piggybacks off of Chuck’s comments. 36:14 – Panelist: Let’s go back to Jest. There is a very common occurrence where we see lots of turn and we see ideas like this has become the dominant or the standard, a lot of people talk about stuff within this community. Then we get this idea that ‘this is the only thing that is happening.’ Transition to jQuery to React to... With that context do you feel like Jest will be a dominant program? Are we going to see Jest used just as common as Mocha and other popular programs? 38:15 – Vitali comments on the panelist’s question. 38:50 – Panelist: New features. Are the features in Jest (over Jasmine, Mocha, etc.) so important that it will drive people to it by itself? 40:30 – Vitali comments on this great question. 40:58 – Panelist asks questions about features about Jest. 41:29 – Vitali talks about this topic. 42:14 – Let’s go to picks! 42:14 – Advertisement. Links: Vitali Zaidman’s Facebook Vitali Zaidman’s Medium Vitali Zaidman’s GitHub Vitali Zaidman’s NPM Vitali Zaidman’s LinkedIn Vitali Zaidman’s Medium Article JavaScript Brutalist Web Design Jasmine Cypress React jQuery Jest Protractor – end to end testing for Angular Test Café Intern Sinon XKCD Sponsors: Kendo UI Sentry Digital Ocean Cache Fly Picks: AJ O’Neal Continuous from last week’s episode: Crossing the Chasm – New Technologies from Niche to General Adaptation. Go Lang Joe Eames Board Game: Rajas of the Ganges Framework Summit Conference in Utah React Conference Aimee Knight Hacker News – “Does Software Understand Complexity” via Michael Feathers Cream City Code Chuck E-Book: How do I get a job? Express VPN Vitali Book: The Square and The Tower: Networks and Power, from the Freemasons to Facebook by Niall Ferguson My article!

Panel: AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guests: Vitali Zaidman In this episode, the panel talks with programmer, Vitali Zaidman, 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 Jest. Show Topics: 1:32 – Chuck: Let’s talk about testing JavaScript in 2018. 1:53 – Vitali talks about solving problems in JavaScript. 2:46 – Chuck asks Vitali a question. 3:03 – Vitali’s answer. 3:30 – Why Jest? Why not Mocha or these other programs? 3:49 – Jest is the best interruption of what testing should look like and the best practice nowadays. There are different options, they can be better, but Jest 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 Cypress, 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 about 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 JavaScript 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 JavaScript 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 – Aimee: “I see that Safari is the new Internet Explorer.” 16:23: Chuck: “Yes, you have to know your audience. Are they using older browsers? What is the compatibility?” 17:01 – Vitali: There are issues with the security. Firefox has a feature of tracking protection; something like that. 17:33 – Question to Vitali by Panelist. 17:55 – Vitali answers the question. 18:30 – Panelist makes additional comments. 18:43 – If you use Safari, you reap what you sow. 18:49 – Chuck: I use Chrome on my iPhone. (Aimee does, too.) Sometimes I wind up in Safari by accident. 19:38 – Panelist makes comments. 19:52 – Vitali tells a funny story that relates to this topic. 20:45 – There are too many standards out there. 21:05 – Aimee makes comments. 21:08 – Brutalist Web Design. Some guy has this site – Brutalist Web Design – where he says use basic stuff and stop being so custom. Stop using the web as some crazy platform, and if your site is a website that can be scrolled through, that’s great. It needs to be just enough for people to see your content. 22:16 – Aimee makes additional comments about this topic of Brutalist Web Design. 22:35 – Panelist: I like it when people go out and say things like that. 22:45 – Here is the point, though. There is a difference between a website and a web application. Really the purpose is to read an article. 23:37 – Vitali chimes in. 24:01 – Back to the topic of content on websites. 25:17 – Panelist: Medium is very minimal. Medium doesn’t feel like an application. 26:10 – Is the website easy enough for the user to scroll through and get the content like they want to? 26:19 – Advertisement. 27:22 – See how far off the topic we got? 27:31 – These are my favorite conversations to have. 27:39 – Vitali: Let’s talk about how my article got so popular. It’s an interesting thing, I started researching “testing” for my company. We wanted to implement one of the testing tools. Instead of creating a presentation, I would write first about it in Medium to get feedback from the community as well. It was a great decision, because I got a lot of comments back. I enjoyed the experience, too. Just write about your problem in Medium to see what people say. 28:48 – Panelist: You put a ton of time and energy in this article. There are tons of links. Did you really go through all of those articles? 29:10 – Yes, what are the most permanent tools? I was just reading through a lot of comments and feedback from people. I tested the tools myself, too! 29:37 – Panelist: You broke down the article, and it’s a 22-minute read. 30:09 – Vitali: I wrote the article for my company, and they ad to read it. 30:24 – Panelist: Spending so much time – you probably felt like it was apart of your job. 30:39 – Vitali: I really like creating and writing. It was rally amazing for me and a great experience. I feel like I am talented in this area because I write well and fast. I wanted to express myself. 31:17 – Did you edit and review? 31:23 – Vitali: I wrote it by myself and some friends read it. There were serious mistakes, and that’s okay I am not afraid of mistakes. This way you get feedback. 32:10 – Chuck: “Some people see testing in JavaScript, and people look at this and say there are so much here. Is there a place where people can start, so that way they don’t’ get too overwhelmed? Is there a way to ease into this and take a bite-size at a time?” 32:52 – Vitali: “Find something that works for them. Read the article and start writing code.” He continues this conversation from here on out. 34:03 – Chuck continues to ask questions and add other comments. 34:16 – Vitali chimes-in.  34:38 – Chuck.  34:46 – Vitali piggybacks off of Chuck’s comments. 36:14 – Panelist: Let’s go back to Jest. There is a very common occurrence where we see lots of turn and we see ideas like this has become the dominant or the standard, a lot of people talk about stuff within this community. Then we get this idea that ‘this is the only thing that is happening.’ Transition to jQuery to React to... With that context do you feel like Jest will be a dominant program? Are we going to see Jest used just as common as Mocha and other popular programs? 38:15 – Vitali comments on the panelist’s question. 38:50 – Panelist: New features. Are the features in Jest (over Jasmine, Mocha, etc.) so important that it will drive people to it by itself? 40:30 – Vitali comments on this great question. 40:58 – Panelist asks questions about features about Jest. 41:29 – Vitali talks about this topic. 42:14 – Let’s go to picks! 42:14 – Advertisement. Links: Vitali Zaidman’s Facebook Vitali Zaidman’s Medium Vitali Zaidman’s GitHub Vitali Zaidman’s NPM Vitali Zaidman’s LinkedIn Vitali Zaidman’s Medium Article JavaScript Brutalist Web Design Jasmine Cypress React jQuery Jest Protractor – end to end testing for Angular Test Café Intern Sinon XKCD Sponsors: Kendo UI Sentry Digital Ocean Cache Fly Picks: AJ O’Neal Continuous from last week’s episode: Crossing the Chasm – New Technologies from Niche to General Adaptation. Go Lang Joe Eames Board Game: Rajas of the Ganges Framework Summit Conference in Utah React Conference Aimee Knight Hacker News – “Does Software Understand Complexity” via Michael Feathers Cream City Code Chuck E-Book: How do I get a job? Express VPN Vitali Book: The Square and The Tower: Networks and Power, from the Freemasons to Facebook by Niall Ferguson My article!

Panel: Charles Max Wood Ward Bell Joe Eames John Papa Special Guests: Shai Reznik In this episode of Adventures in Angular, the panel talks to Shai Reznik about TDD. TDD is a technique used to write unit tests. They discuss what exactly unit testing is, the benefits of it, and why you would want to use it to test your code. Shai then discusses what TDD is, why you would use it, the benefits of it, and how you can get started using TDD in your own code. He loves that he can use TDD as a design tool for code and that it forces you to write cleaner, more modular code. In particular, we dive pretty deep on: What is TDD? Test Driven Development What is unit testing? Benefits of unit testing Faster feedback and saves you from regression bugs JavaScript Unit Testing & TDD Theory by Shai Red, Green, Refactor Why would you want to use TDD? Benefits of TDD You actually get to write the tests Forces you to write more modular and cleaner code Use TDD as a design tool for code Do you actually write code using TDD? Angular Ember Production code vs other types of code Write tests around assumptions Is TDD Dead? YouTube Series Allows you to think through what you want to build before you build it Blueprint in a sense Testing vs TDD And much, much more! Links:  Angular JavaScript Unit Testing & TDD Theory by Shai TDD Ember Is TDD Dead? YouTube Series NgConf HighRez.io   Picks: Charles Get involved in the political process John Don’t be afraid to have healthy discussions Five Things The 7 Ds of Development Talk Joe The Mistakes I Made As a Beginner Programmer by Samer Buna An Overview of JavaScript Testing in 2018 by Vitali Zaidman Try it out and decide for yourself Ward NgRx Data Shai Machine Learning-Driven Bundling by Minko Gechev Angular TDD course coming soon JavaScript Unit Testing & TDD Theory

Panel: Charles Max Wood Ward Bell Joe Eames John Papa Special Guests: Shai Reznik In this episode of Adventures in Angular, the panel talks to Shai Reznik about TDD. TDD is a technique used to write unit tests. They discuss what exactly unit testing is, the benefits of it, and why you would want to use it to test your code. Shai then discusses what TDD is, why you would use it, the benefits of it, and how you can get started using TDD in your own code. He loves that he can use TDD as a design tool for code and that it forces you to write cleaner, more modular code. In particular, we dive pretty deep on: What is TDD? Test Driven Development What is unit testing? Benefits of unit testing Faster feedback and saves you from regression bugs JavaScript Unit Testing & TDD Theory by Shai Red, Green, Refactor Why would you want to use TDD? Benefits of TDD You actually get to write the tests Forces you to write more modular and cleaner code Use TDD as a design tool for code Do you actually write code using TDD? Angular Ember Production code vs other types of code Write tests around assumptions Is TDD Dead? YouTube Series Allows you to think through what you want to build before you build it Blueprint in a sense Testing vs TDD And much, much more! Links:  Angular JavaScript Unit Testing & TDD Theory by Shai TDD Ember Is TDD Dead? YouTube Series NgConf HighRez.io   Picks: Charles Get involved in the political process John Don’t be afraid to have healthy discussions Five Things The 7 Ds of Development Talk Joe The Mistakes I Made As a Beginner Programmer by Samer Buna An Overview of JavaScript Testing in 2018 by Vitali Zaidman Try it out and decide for yourself Ward NgRx Data Shai Machine Learning-Driven Bundling by Minko Gechev Angular TDD course coming soon JavaScript Unit Testing & TDD Theory

Panel: Charles Max Wood Ward Bell Joe Eames John Papa Special Guests: Shai Reznik In this episode of Adventures in Angular, the panel talks to Shai Reznik about TDD. TDD is a technique used to write unit tests. They discuss what exactly unit testing is, the benefits of it, and why you would want to use it to test your code. Shai then discusses what TDD is, why you would use it, the benefits of it, and how you can get started using TDD in your own code. He loves that he can use TDD as a design tool for code and that it forces you to write cleaner, more modular code. In particular, we dive pretty deep on: What is TDD? Test Driven Development What is unit testing? Benefits of unit testing Faster feedback and saves you from regression bugs JavaScript Unit Testing & TDD Theory by Shai Red, Green, Refactor Why would you want to use TDD? Benefits of TDD You actually get to write the tests Forces you to write more modular and cleaner code Use TDD as a design tool for code Do you actually write code using TDD? Angular Ember Production code vs other types of code Write tests around assumptions Is TDD Dead? YouTube Series Allows you to think through what you want to build before you build it Blueprint in a sense Testing vs TDD And much, much more! Links:  Angular JavaScript Unit Testing & TDD Theory by Shai TDD Ember Is TDD Dead? YouTube Series NgConf HighRez.io   Picks: Charles Get involved in the political process John Don’t be afraid to have healthy discussions Five Things The 7 Ds of Development Talk Joe The Mistakes I Made As a Beginner Programmer by Samer Buna An Overview of JavaScript Testing in 2018 by Vitali Zaidman Try it out and decide for yourself Ward NgRx Data Shai Machine Learning-Driven Bundling by Minko Gechev Angular TDD course coming soon JavaScript Unit Testing & TDD Theory

This talk will be a comprehensive look at what you need to know to properly test your web applications on mobile devices. We’ll look at the different mobile phones that exist, what browsers they run, and what you can do to support them. Additionally we’ll examine some of the testing tools that can be used to make the whole process much easier. John Resig is a JavaScript Tool Developer for the Mozilla Corporation and the author of the book Pro JavaScript Techniques. He’s also the creator and lead developer of the jQuery JavaScript library. Currently, John is located in Boston, MA. He’s hard at work on his second book, Secrets of the JavaScript Ninja, due in bookstores in 2009. Follow John on Twitter: @jeresig Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).