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(735)

JSJ 323: "Building a JavaScript platform that gives you the power to build your own CDN" with Kurt Mackey

JSJ 323: "Building a JavaScript platform that gives you the power to build your own CDN" with Kurt Mackey

Panel: Charles Max WoodAJ ONeal Special Guests: Kurt MackeyIn this episode, the JavaScript Jabber panel talks to Kurt Mackey about Fly.io. At Fly.io, they are "building a JavaScript platform that gives you the power to build your own CDN." They talk about how Fly.io came to fruition, how CDN caching works, and what happens when you deploy a Fly app. They also touch on resizing images with Fly, how you actually build JavaScript platforms using Fly, and more!In particular, we dive pretty deep on:Fly.ioBuilding a programmable CDNHigh level overview of Fly.ioHow did this project come together?CDNs didn’t work with dynamic applicationsHas been working on this since 2008Extend application logic to the “edge”Putting burden of JavaScript “nastiest” onto the web serverFly is the proxy layerGetting things closer to visitors and usersCDN cachingCache APIsWriting logic to improve your lighthouse scoreHave you built in resizing images into Fly?Managing assets closer to the userCan you modify your own JavaScript files?What happens when you deploy a Fly appHaving more application logicDOM within the proxyGhostReact and GatsbyIntelligently loading client JavaScriptHow do you build the JavaScript platform?And much, much more!Links:Fly.ioJavaScriptGhostGatsbyReact@flydotio@mrkurtKurt at ARS TechnicaKurt’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesGitLabAJGiteaBlack PantherKurtPacket.netThe Three-Body Problem by Cixin LiuSupport 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 Heinä 20181h 3min

JSJ 322: Building SharePoint Extensions with JavaScript with Vesa Juvonen LIVE at Microsoft Build

JSJ 322: Building SharePoint Extensions with JavaScript with Vesa Juvonen LIVE at Microsoft Build

Panel: Charles Max Wood Special Guests: Vesa JuvonenIn this episode, the JavaScript Jabber panel talks to Vesa Juvonen about building SharePoint extensions with JavaScript. Vesa is on the SharePoint development team and is responsible for the SharePoint Framework, which is the modern way of implementing SharePoint customizations with JavaScript. They talk about what SharePoint is, why they chose to use JavaScript with it, and how he maintains isolation. They also touch on the best way to get started with SharePoint, give some great resources to help you use it, and more!In particular, we dive pretty deep on:Vesa introWhat is SharePoint?Has existed since 2009People either know about it and use it or don’t know what it isBaggage from a customization perspectiveWhy JavaScript developers?Modernizing developmentSharePoint FrameworkMicrosoft Ignite ConferenceIs there a market for it?System integratorsAngular Element and ReactReact for SharePoint Framework back-endSupports VueReact Round Up PodcastHow do you maintain isolation?What’s the best way to get started with SharePoint extensions?Office 365 Developer ProgramSharePoint documentationSharePoint YouTubeWhat kinds of extensions are you seeing people build?And much, much more!Links:SharePointJavaScriptSharePoint FrameworkMicrosoft Ignite ConferenceAngular ElementReactVueReact Round Up PodcastOffice 365 Developer ProgramSharePoint documentationSharePoint YouTube @OfficeDev@vesajuvonenVesa’s blogVesa’s GitHub@SharePointSponsorsKendo UISentryDigital OceanPicks:CharlesZig ZiglarConversations with My Dog by Zig ZiglarPimsleur Lessons on AudibleVesaArmada by Ernest ClineSupport 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.

17 Heinä 201831min

JSJ 321: Babel and Open Source Software with Henry Zhu

JSJ 321: Babel and Open Source Software with Henry Zhu

Panel: Charles Max WoodAimee KnightAJ ONealJoe Eames Special Guests: Henry ZhuIn this episode, the JavaScript Jabber panel talks to Henry Zhu about Babel and open source software. Henry is one of the maintainers on Babel, which is a JavaScript compiler, and recently left this job to work on doing open source full time as well as working on Babel. They talk about where Babel is today, what it actually is, and his focus on his open source career. They also touch on how he got started in open source, his first PR, and more!In particular, we dive pretty deep on:Henry introBabel updateSebastian McKenzie was the original creator of BabelHas learned a lot about being a maintainerWhat is Babel?JavaScript compilerYou never know who your user isHas much changed with Babel since Sebastian left?Working on open sourceHow did you get started in pen source?The ability to learn a lot from open sourceAtrocities of globalizationMore decentralization from GitHubGitea and GitLabGitea installerOpen source is more closed nowHis first PRJSCSAuto-fixingPrettierLearning more about lintingYou don’t have to have formal training to be successfulCodefund.ioSustainability of open sourceAnd much, much more!Links:BabelJavaScriptGiteaGitLabGitea installerPrettierCodefund.io@left_padHenry’s GitHubhenryzoo.comHenry’s PatreonSponsorsKendo UISentryDigital OceanPicks:CharlesOrphan BlackCrucial Accountability by Kerry PattersonAimeeDesk with cubby holes for catsThe Key to Good Luck Is an Open Mind blog postAJGiteaGitea installerGreenlockJoeSoloJustifiedHenryCelesteZeit Day talksSupport 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.

10 Heinä 201857min

JSJ 320: Error Tracking and Troubleshooting Workflows with David Cramer LIVE at Microsoft Build

JSJ 320: Error Tracking and Troubleshooting Workflows with David Cramer LIVE at Microsoft Build

Panel: Charles Max WoodAlyssa NichollWard Bell Special Guests: David CramerIn this episode, the JavaScript Jabber panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more!In particular, we dive pretty deep on:David introFounder and CEO of SentryWhat is Sentry?Working with PHPDe-bugger for productionFocus on workflowGoal of SentryTriaging the problemWorkflow managementSentry started off as an open-source side projectInstrumentation for JavaScriptEmber, Angular, and npmGot their start in PythonLogsTotally open-sourceMost compatible with run-timeCan work with any languageDeep contextsDetermining the root causeAnd much, much more!Links:SentryJavaScriptEmberAngularnpmPythonSentry’s GitHub@getsentryDavid’s GitHubDavid’s Website@zeegSponsorsKendo UIFreshBooksLoot CratePicks:CharlesSocks as SwagDavidVS CodeKubernetesSupport 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.

3 Heinä 201827min

JSJ 319: Winamp2-js with Jordan Eldredge

JSJ 319: Winamp2-js with Jordan Eldredge

Panel: Charles Max WoodAJ ONealAimee KnightJoe Eames Special Guests: Jordan EldredgeIn this episode, the JavaScript Jabber panelists discuss Winamp2-js with Jordan Eldredge. Jordan is the creator of Winamp2-js and was inspired to create this media player from the old Winamp media player that he used back in the day. They talk about the importance of limitations, the value of having fun side projects, and pushing the boundaries. They also touch on skin parsing, making Webamp an electron app, and more!In particular, we dive pretty deep on:What is Winamp2-js?The history and future of WinampWACUPWinamp was the first big mp3 player that you could styleWebamp’s features and the technical challenges associated with themWhy JavaScript?Creative solutionsLimitations of browser and creating something that previously existedThe importance of limitationsHadn’t done very much JavaScript prior to this projectOriginally created with jQueryLed him into a career in JavaScriptPushing the boundariesSkin parsing“Bitrot” and making Winamp skins accessible againThe value of side projects, even stupid onesArchitecture docsWhat made you choose React and Redux?Spotiamp (Soptify’s canceled Winamp client)Making Webamp an Electron appWinamp visualizers being ported to the webThe domain name webamp.orgAnd much, much more!Links:Winamp2-jsWebampJavaScriptjQueryArchitecture docsReactReduxjordaneldredge.comJordan’s GitHub@captbaritoneSponsorsKendo UIFreshBooksLoot CratePicks:CharlesJAM XT SpeakerTrelloAJSamson GoMicGreenlock for Web ServersGreenlock for Node.jsAimeeKA Engineering PrinciplesJoe2ality.comWhat if JavaScript wins? Medium postJordanJavaScript GardenRust@winampskinsSupport 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 Kesä 201848min

JSJ 318: Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari LIVE at Microsoft Build

JSJ 318: Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari LIVE at Microsoft Build

Panel: Charles Max Wood Special Guests: Ori Zohar and Gopinath ChigakkagariIn this episode, the JavaScript Jabber panelists discuss Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari at Microsoft Build. Ori is on the product team at VSTS focusing on DevOps specifically on Azure. Gopinath is the group program manager in VSTS primarily working on continuous integration, continuous delivery, DevOps, Azure deployment, etc. They talk about the first steps people should take when getting into DevOps, define DevOps the way Microsoft views it, the advantages to automation, and more!In particular, we dive pretty deep on:Ori and Gopi introVSTS – Visual Studio Team ServicesVSTS gives developers the ability to be productiveDeveloper productivityWhat’s the first big step people should be taking if they’re getting into DevOps?The definition of DevOpsThe people and the processes as the most important pieceDevOps as the best practicesAutomating processesWhat people do when things go wrong is what really countsLetting the system take care of the problemsHave the developers work on what they are actually getting paid forTrend of embracing DevOpsShifting the production responsibility more onto the developer’sIncentivizing developersPeople don’t account for integrationContinuous integrationTrends on what customers are asking forSafetyDocker containersAnd much, much more!Links:AzureMicrosoft BuildVSTS@orizhrOri’s GitHubGopi’s GitHub@gopinachSponsorsKendo UILinodeFreshBooksPicks:Charles.NET Rocks!Shure SM58 MicrophoneZoom H6OriFitbitPacific Northwest HikingGopinathSeattle, WASupport 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.

18 Kesä 201856min

JSJ 317: Prisma with Johannes Schickling

JSJ 317: Prisma with Johannes Schickling

Panel: Charles Max WoodAJ O’Neal Special Guests: Johannes SchicklingIn this episode, the JavaScript Jabber panelists discuss Prisma with Johannes Schickling. Johannes is the CEO and co-founder of GraphCool and works with Prisma. They talk about the upcoming changes within GraphCool, what Prisma is, and GraphQL back-end operations. They also touch on the biggest miscommunication about Prisma, how Prisma works, and much more!In particular, we dive pretty deep on:JSJ Episode 257 MJS Episode 055Raised a seed roundRebranding of GraphCoolWhat are you wanting to do with the seed money you raised?Focused on growing his team currentlyMaking GraphQL easier to doThe change in the way people build softwareWhat is Prisma?Two things you need to do as you want to adopt GraphQLApollo Client and RelayGraphQL on the back-endResolversResolving data in one queryPrisma supports MySQL and PostgreSQLHow do you control access to the GraphQL endpoint that Prisma gives you?Biggest miscommunication about PrismaPrisma makes it easier for you to make your own GraphQL serverApplication schemasHow do you blend your own resolvers with Prisma?And much, much more!Links:JSJ Episode 257 MJS Episode 055GraphCoolPrismaGraphQLApollo ClientRelayMySQLPostgreSQL@schicklingJohannes’ GitHubSchickling.mePrisma SlackSponsorsKendo UILinodeFreshBooksPicks:CharlesAudibleThe 5 Love Languages of Children by Gary ChapmanFacebook Backyard Homesteader GroupsCharlesMaxWood.comSling TVRoku ExpressAJThe Legend of Zelda: Breath of the WildJohannesFigmaNetlify FunctionsGraphQL EuropeSupport 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.

12 Kesä 201849min

JSJ 316: Visual Studio Code with Rachel MacFarlane and Matt Bierner LIVE at Microsoft Build

JSJ 316: Visual Studio Code with Rachel MacFarlane and Matt Bierner LIVE at Microsoft Build

Panel: Charles Max Wood Special Guests: Rachel MacFarlane and Matt BiernerIn this episode, the JavaScript Jabber panelists discuss Visual Studio Code with Rachel MacFarlane and Matt Bierner, who are both developers on Visual Studio Code. They talk about what the workflow at Visual Studio Code looks like, what people can look forward to coming out soon,  and how people can follow along the VS Code improvements on GitHub and Twitter. They also touch on their favorite extensions, like the Docker extension and the Azure extension and their favorite VS Code features.In particular, we dive pretty deep on:Rachel and Matt introMonth to month workflow of Visual Studio CodeVS Code JavaScript, TypeScript, and Mark Down supportWorking on GitHub and within the communityCheck out new features incrementally with insidersCommunity driven workWhat is coming out in Visual Studio Code?GitHub helps to determine what they work onWorking on Grid ViewImproved settings UIHighlighting unused variables in your codeImprovements with JS DocsDartVisual Studio Extension APIHow do people follow along with the VS Code improvements?Follow along on GitHub and TwitterDownload VS Code InsidersHave a general road map of what the plan is for the yearTechnical debt weekWhat do you wish people knew about VS Code?Favorite extensionsDocker extension and Azure extensionAnd much, much more!Links:Visual Studio CodeJavaScriptTypeScriptDartVS Code GitHub@CodeVS Code InsidersDocker extensionAzure extensionRachel’s GitHubMatt’s GitHubMattBierner.com@mattbiernerSponsorsKendo UILinodeFreshBooksPicks:CharlesOrphan BlackAvengers: Infinity WarFishingRachelGitLensMattThe Bronx WarriorsSupport 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.

5 Kesä 201835min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
mimmit-sijoittaa
psykopodiaa-podcast
rss-rahapodi
ostan-asuntoja-podcast
rss-lahtijat
pomojen-suusta
taloudellinen-mielenrauha
oppimisen-psykologia
rahapuhetta
sijoituspodi
rss-seuraava-potilas
kasvun-kipuja
rss-viisas-raha-podi
rss-neuvottelija-sami-miettinen
io-techin-tekniikkapodcast
sijoitusovi-podcast
rss-uskalla-yrittaa
rss-h-asselmoilanen
rss-merja-mahkan-rahat