JSJ 341: Testing in JavaScript with Gil Tayar
JavaScript Jabber27 Marras 2018

JSJ 341: Testing in JavaScript with Gil Tayar

Panel:
  • Aimee Knight
  • AJ O’Neal
  • Charles Max Wood
Special Guest: Gil Tayar In this episode, the panel talks with Gil Tayar who is currently residing in Tel Aviv and is a software engineer. He is currently the Senior Architect at Applitools in Israel. The panel and the guest talk about the different types of tests and when/how one is to use a certain test in a particular situation. They also mention Node, React, Selenium, Puppeteer, and much more!Show Topics:0:00 – Advertisement: KENDO UI 0:35 – Chuck: Our panel is AJ, Aimee, myself – and our special guest is Gil Tayar. Tell us why you are famous!1:13 – Gil talks about where he resides and his background. 2:27 – Chuck: What is the landscape like now with testing and testing tools now?2:39 – Guest: There is a huge renaissance with the JavaScript community. Testing has moved forward in the frontend and backend. Today we have lots of testing tools. We can do frontend testing that wasn’t possible 5 years ago. The major change was React.The guest talks about Node, React, tools, and more!4:17 – Aimee: I advocate for tests and testing. There is a grey area though...how do you treat that? If you have to get something into production, but it’s not THE thing to get into production, does that fall into product or...what?5:02 – Guest: We decided to test everything in the beginning. We actually cam through and did that and since then I don’t think I can use the right code without testing. There are a lot of different situations, though, to consider.The guest gives hypothetical situations that people could face. 6:27 – Aimee.6:32 – Guest: The horror to changing code without tests, I don’t know, I haven’t done that for a while. You write with fear in your heart. Your design is driven by fear, and not what you think is right. In the beginning don’t write those tests, but...7:22 – Aimee: I totally agree and I could go on and on and on.7:42 – Panel: I want to do tests when I know they will create value. I don’t want to do it b/c it’s a mundane thing. Secondly, I find that some times I am in a situation where I cannot write the test b/c I would have to know the business logic is correct. I am in this discovery mode of what is the business logic? I am not just building your app.I guess I just need advice in this area, I guess.8:55 – Guest gives advice to panelist’s question. He mentions how there are two schools of thought.10:20 – Guest: Don’t mock too much.10:54 – Panel: Are unit tests the easiest? I just reach for unit testing b/c it helps me code faster. But 90% of my code is NOT that.11:18 – Guest: Exactly! Most of our test is glue – gluing together a bunch of different stuff! Those are best tested as a medium-sized integration suite.12:39 – Panel: That seems like a lot of work, though! I loathe the database stuff b/c they don’t map cleanly. I hate this database stuff.13:06 – Guest: I agree, but don’t knock the database, but knock the level above the database.13:49 – Guest: Yes, it takes time! Building the script and the testing tools, but when you have it then adding to it is zero time. Once you are in the air it’s smooth sailing.14:17 – Panel: I guess I can see that. I like to do the dumb-way the first time. I am not clear on the transition.14:47 – Guest: Write the code, and then write the tests.The guest gives a hypothetical situation on how/when to test in a certain situation. 16:25 – Panel: Can you talk about that more, please?16:50 – Guest: Don’t have the same unit – do browser and business logic stuff separated. The real business logic stuff needs to be above that level. First principle is separation of concerns.18:04 – Panel talks about dependency interjection and asks a question. 18:27 – Guest: What I am talking about very, very light inter-dependency interjection.19:19 – Panel: You have a main function and you are doing requires in the main function. You are passing the pieces of that into the components that need it.19:44 – Guest: I only do it when it’s necessary; it’s not a religion for me. I do it only for those layers that I know will need to be mocked; like database layers, etc.20:09 – Panel.20:19 – Guest: It’s taken me 80 years to figure out, but I have made plenty of mistakes a long the way. A test should run for 2-5 minutes max for package.20:53 – Panel: What if you have a really messy legacy system? How do you recommend going into that? Do you write tests for things that you think needs to get tested?21:39 – Guest answers the question and mentions Selenium! 24:27 – Panel: I like that approach.24:35 – Chuck: When you say integration test what do you mean?24:44 – Guest: Integration tests aren’t usually talked about. For most people it’s tests that test the database level against the database. For me, the integration tests are taking a set of classes as they are in the application and testing them together w/o the...so they can run in millisecond time.26:54 – Advertisement – Sentry.io 27:52 – Chuck: How much do the tools matter?28:01 – Guest: The revolutions matter. Whether you use Jasmine or Mocha or whatever I don’t think it matters. The tests matter not the tools.28:39 – Aimee: Yes and no. I think some tools are outdated.28:50 – Guest: I got a lot of flack about my blog where I talk about Cypress versus Selenium. I will never use Jasmine. In the end it’s the29:29 – Aimee: I am curious would you be willing to expand on what the Selenium folks were saying about Puppeteer and others may not provide?29:54 – Guest: Cypress was built for frontend developers. They don’t care about cross browser, and they tested in Chrome. Most browsers are typically the same. Selenium was built with the QA mindset – end to end tests that we need to do cross browser.The guest continues with this topic.30:54 – Aimee mentions Cypress. 31:08 – Guest: My guessing is that their priority is not there. I kind of agree with them.31:21 – Aimee: I think they are focusing on mobile more.31:24 – Guest: I think cross browser testing is less of an issue now. There is one area that is important it’s the visual area! It’s important to test visually across these different browsers.32:32 – Guest: Selenium is a Swiss knife – it can do everything.33:32 – Chuck: I am thinking about different topics to talk about. I haven’t used Puppeteer. What’s that about?33:49 – Guest: Puppeteer is much more like Selenium. The reason why it’s great is b/c Puppeteer will always be Google Chrome. 35:42 – Chuck: When should you be running your tests? I like to use some unit tests when I am doing my development but how do you break that down?36:06 – Guest.38:30 – Chuck: You run tests against production?38:45 – Guest: Don’t run tests against production...let me clarify!39:14 – Chuck.39:21 – Guest: When I am talking about integration testing in the backend...40:37 – Chuck asks a question. 40:47 – Guest: I am constantly running between frontend and backend.I didn’t know how to run tests for frontend. I had to invent a new thing and I “invented” the package JS DONG. It’s an implementation of Dong in Node. I found out that I wasn’t the only one and that there were others out there, too.43:14 – Chuck: Nice! You talked in the prep docs that you urged a new frontend developer to not run the app in the browser for 2 months?43:25 – Guest: Yeah, I found out that she was running the application...she said she knew how to write tests. I wanted her to see it my way and it probably was a radical train-of-thought, and that was this...44:40 – Guest: Frontend is so visual.45:12 – Chuck: What are you working on now?45:16 – Guest: I am working with Applitools and I was impressed with what they were doing.The guest goes into further detail.46:08 – Guest: Those screenshots are never the same.48:36 – Panel: It’s...comparing the output to the static site to the...48:50 – Guest: Yes, that static site – if you have 30 pages in your app – most of those are the same. We have this trick where we don’t upload it again and again. Uploading the whole static site is usually very quick. The second thing is we don’t wait for the results. We don’t wait for the whole rendering and we continue with the

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Jaksot(734)

Mastering Back-End Functionalities and Development with AWS Amplify - JSJ 619

Mastering Back-End Functionalities and Development with AWS Amplify - JSJ 619

In this episode, Steve delves into a deep and insightful conversation with Erik Hanchett from Amazon AWS. They explore a wide range of topics, from discussing the possibilities and complexities of using multiple software services for back-end development to unraveling the benefits of using services like AWS Amplify for handling multiple tasks and integrated functionalities. The conversation also touches on the development and deployment processes, local testing environment setup, language choices, and the Vue component library with connected components and theming. Erik shares his vast expertise and knowledge in the field, and the engaging dialogue offers valuable insights and recommendations for both experienced and aspiring developers.SponsorsChuck's Resume Template Raygun - Application Monitoring For Web & Mobile AppsBecome a Top 1% Dev with a Top End Devs MembershipSocialsLinkedIn: Erik Hanchett PicksErik - Apple Vision ProSteve - Why You’ve Never Been In A Plane CrashSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

6 Helmi 20241h 10min

Exploring AI Impact on Code Generation and Quality Metrics - JSJ 618

Exploring AI Impact on Code Generation and Quality Metrics - JSJ 618

Conor Bronsdon is the host of the Dev Interrupted Podcast and currently works at LinearB. They dive into the world of generative AI tools in software development, exploring the impact, challenges, and potential benefits they present. They engage in a lively discussion about the use of AI tools like Copilot and the implications for code generation, team efficiency, and happiness. The conversation also touches on the concerns and considerations surrounding AI integration in coding, including compliance, quality, and intellectual property. Join them as they delve into the evolving landscape of AI in software development, the quest for improved developer experiences, and ethical considerations.SponsorsChuck's Resume Template Developer Book Club Become a Top 1% Dev with a Top End Devs MembershipLinksDev InterruptedSocialsLinkedIn: Conor BronsdonConor BronsdonPicksAJ - Market Saturation = 98.9% - What Now?AJ - Mentour PilotAJ - Keychain Pin ToolAJ - Open AudibleConor - Feel-Good Productivity: How to Do More of What Matters to YouSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

30 Tammi 20241h 6min

Inside the World of React: Server Components, Unidirectional Data Flow, and Frameworks - JSJ 617

Inside the World of React: Server Components, Unidirectional Data Flow, and Frameworks - JSJ 617

Sam Selikoff is the founder of Build UI, Inc. They unpack a myriad of discussions surrounding JavaScript and its applications. They delve into topics such as RPC resurgence, React server components, and the challenges and solutions around integrating design and components. A variety of technical concepts, tools, and frameworks, including Tailwind, Redux, and Remix, are also explored. Additionally, the episode touches upon important mental health conversations, personal experiences, and the pitfalls of fragmented media subscriptions. SponsorsChuck's Resume Template Developer Book Club Become a Top 1% Dev with a Top End Devs MembershipSocialsTwitter: @samselikoffPicksAJ - No BackendAJ - Home AssistantAJ - CloudFreeAJ - AmeriDroidAJ - Chaos WalkingDan - Blue Eye SamuraiDan - Samurai JackSam - Lessons in ChemistrySupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

23 Tammi 20241h 22min

Streamlining AI Integration - JSJ 616

Streamlining AI Integration - JSJ 616

Ismail Pelaseyed is the co-founder of Superagent. They delve into the world of AI technology, open-source frameworks, and the practical applications of AI assistants. The conversation covers a range of topics, from the technical and philosophical differences between AI frameworks to the importance of user-facing UI components with the power of AI. They also talk about the practical use cases of Superagent, its potential impact on the AI industry, and the challenges and considerations surrounding the deployment and monetization of open-source projects.SponsorsChuck's Resume Template Raygun - Application Monitoring For Web & Mobile AppsBecome a Top 1% Dev with a Top End Devs MembershipLinksSuperagentSocialsLinkedIn: Ismail PelaseyedPicksAJ - His & Her BidetAJ - Ollama (Installer)AJ - Home AssistantAJ - Chaos Walking (Books)AJ - Market Saturation = 98.9% - What Now?AJ - Keychain Pin ToolCharles - Disney ChronologyCharles - once.comDan - PrometheusDan - Which one is the un-React?Ismail - Fargoismail - outlinesSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

16 Tammi 20241h 17min

Iterating on Open Source - JSJ 615

Iterating on Open Source - JSJ 615

Today the panel is discussing iterating on open source projects. Aimee and AJ recall a conversation they had in the past on this subject and AJ talks about some of his experience iterating with open source. AJ believes that we have an obligation to capture the value of what you create so that we can reinvest and create more value, though he admits that making money in open source is a unique challenge because donations only really work if you have a project that gets billions of downloads a month. As your project grows, it has to change in order to survive, and eventually you will need to get financial support from your project. The panel agrees that some of the main issues with iterating in open source are maintaining the code and getting feedback from users, financial backing, and roadmapping and integrations.The panel discusses their methods for getting feedback from their users. This feedback is valuable because it can show you things that you missed. They acknowledge that there can be conflicts of interest between those who only use the project and those who financially support it, and you have to make a choice. Unfortunately, someone is probably going to be inconvenienced no matter what choice you make. When making these decisions, you have to consider who it helps, who it frustrates, and who it may cause problems for. The panelists talk about different ways they’ve handled making these decisions in the past. The JavaScript experts talk about the importance of having data on your user base in order to make good choices for your users. They talk about different methods for notifying your users of upcoming changes and how it will affect compatibility, and some of the challenges with communicating with your users. AJ talks about an iteration he thought was a good idea but that a lot of people hated and how he noticed that the new users liked it but the old users did not. They panel agrees that people in general don’t like change. AJ talks about what he learned from this experience. Another common issue is integrating with other services. Integrating with cloud services, or at least giving people the option to integrate gives you an opportunity to reach more people and maintain the project long term. AJ gives some final thoughts to close the show, namely that most projects never go anywhere, and that’s ok. If you’ve got something that starts going somewhere, think early on about how you can better serve the community and remember that these people are mostly grateful and semi-willing to support you. He believes that if you are helping people create value, you deserve to see the fruits of your labor. He advises listeners to stay true to your open source ideals, think about your users perspective, and that the earlier you can think about this and make these choices, the better it is for your project SponsorsChuck's Resume Template Developer Book Club Become a Top 1% Dev with a Top End Devs MembershipLinksHow-npm-am-iReactVue.jsLet’s EncryptAsync/awaitNodePicksAimee - Debug Like a NinjaSteve - Jack Ryan AJ - Why I, as a black man, attend KKK meetingsCharles - It’s a Wonderful LifeCharles - Mr. Kreuger’s ChristmasSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

9 Tammi 202457min

Dev Dilemmas: TypeScript Triumphs and Quirks of JavaScript Arrays - JSJ 614

Dev Dilemmas: TypeScript Triumphs and Quirks of JavaScript Arrays - JSJ 614

AJ, Charles, Dan, and Steve dive deep into all things JavaScript and TypeScript. In this episode, they discuss the pros and cons of arrow functions and the ongoing debate about using semicolons at the end of JavaScript statements. They also explore the use of different types of quotes for strings and the rise in popularity of TypeScript among developers. Additionally, they cover a wide range of topics, including array manipulation, coding laziness, and the challenges of reading and understanding JavaScript code. Join them as they navigate through these intriguing discussions and gather valuable insights for our development journey.SponsorsChuck's Resume Template Raygun - Application Monitoring For Web & Mobile AppsBecome a Top 1% Dev with a Top End Devs MembershipPicksAJ - Chaos Walking: The Complete Trilogy: Books 1-Charles - SaltconCharles - MysteriumDan - CatanDan - Documentary about the history of Zionism and the founding of Israel: "Pillar of Fire"Steve - How archaeologists reconstructed the burning of Jerusalem in 586 BCESupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

2 Tammi 20241h 33min

The Future of Authentication in JavaScript: An Inside Look into Passport JS with Jared Hanson - JSJ 613

The Future of Authentication in JavaScript: An Inside Look into Passport JS with Jared Hanson - JSJ 613

Jared Hanson is a software engineer at Okta. In this episode, they delve into the world of authentication strategies, troubleshooting touchscreen frustrations, and exploring the evolution of web application technology. They touch on the challenges of secure authentication, the complexity of JavaScript type checking, and the intersection of security and usability in technologies like WebAuthn. Join us as they discuss their experiences with Passport JS, the potential of WebAuthn, the frustration with ongoing changes in browser technology, and much more. Tune in for an insightful discussion on cutting-edge trends in the JavaScript and Node.js ecosystems!SponsorsChuck's Resume Template Developer Book Club Become a Top 1% Dev with a Top End Devs MembershipSocialsLinkedIn: Jared HansonTwitter: @jaredhansonPicksAJ - SQL <---> Types <---> JShttps://github.com/nettofarah/postgres-schema-tshttps://www.npmjs.com/package/ts-to-jsdochttps://jswithtypes.com/AJ - Creative T60 SpeakersAJ - HammerHead Metal Shower HeadAJ - Degrees of Comfort King Dual-Heated BlanketCharles - Risk Legacy | Board GameCharles - Ubiquiti: UniFi - IntroductionSteve - The DriveSteve - FigmaSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

26 Joulu 20231h 19min

The Rise of No Code: A Deep Dive into Toddle's Revolutionary Web App Platform - JSJ 612

The Rise of No Code: A Deep Dive into Toddle's Revolutionary Web App Platform - JSJ 612

Andreas Møller is a software engineer and the creator of Toddle, a platform that lets you build web applications without traditional code. They dive into the world of web development and the exciting rise of no-code and low-code approaches. They discuss the power and complexity of Toddle, its unique visual programming language, and how it enables efficient web development. They talk about the nitty-gritty of visual programming and the complexities of version control, so stick around and join us for this deep dive into the ever-evolving world of web development.SponsorsChuck's Resume Template Raygun - Application Monitoring For Web & Mobile AppsMiroBecome a Top 1% Dev with a Top End Devs MembershipLinksToddle SocialsLinkedIn: Andreas MøllerPicksAJ - A Man Called OttoAJ - Jonathan BlowDan - Dan's tweet about Jesus being a Jew from JudeaDan - Lucky Hank TV showSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

19 Joulu 20231h 21min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
psykopodiaa-podcast
rss-rahapodi
mimmit-sijoittaa
inderespodi
taloudellinen-mielenrauha
ostan-asuntoja-podcast
rss-bisnesta-bebeja
pomojen-suusta
rss-rahamania
lakicast
rss-sisalto-kuntoon
rss-seuraava-potilas
rss-paasipodi
herrasmieshakkerit
juristipodi
jahtaa-unelmiasi
rss-ammattipodcast
rss-salonkipodi
rss-karon-grilli