JSJ 331: “An Overview of JavaScript Testing in 2018” with Vitali Zaidman
JavaScript Jabber - Un pódcast de Charles M Wood - Martes
Categorías:
Panel:
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:
Picks:
AJ O’Neal
- Continuous from last week’s episode: Crossing the Chasm – New Technologies from Niche to General Adaptation.
- Go Lang
Joe Eames
Aimee Knight
Chuck
Vitali
