LivesetDB

JSJ 341: Testing in JavaScript with Gil Tayar

1 h 0357 tracks

Source: archive.org
00:001:02:49

Tracklist

57 tracks
As playlist
  1. 1Advertisement: KENDO UI00
  2. 2and our special guest is Gil Tayar. Tell us why you are famous!Chuck: Our panel is AJ, Aimee, myself
  3. 3Gil talks about where he resides and his background.13
  4. 4Chuck: What is the landscape like now with testing and testing tools now?27
  5. 5Aimee.27
  6. 6Aimee: I totally agree and I could go on and on and on.22
  7. 7Guest gives advice to panelist’s question. He mentions how there are two schools of thought.55
  8. 8Guest: Don’t mock too much.20
  9. 9Panel: 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.54
  10. 10gluing together a bunch of different stuff! Those are best tested as a medium-sized integration suite.Guest: Exactly! Most of our test is glue
  11. 11Panel: 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.39
  12. 12Guest: I agree, but don’t knock the database, but knock the level above the database.06
  13. 13Guest: 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.49
  14. 14Panel: I guess I can see that. I like to do the dumb-way the first time. I am not clear on the transition.17
  15. 15Guest: Write the code, and then write the tests.47
  16. 16Panel: Can you talk about that more, please?25
  17. 17do browser and business logic stuff separated. The real business logic stuff needs to be above that level. First principle is separation of concerns.Guest: Don’t have the same unit
  18. 18Panel talks about dependency interjection and asks a question.04
  19. 19Guest: What I am talking about very, very light inter-dependency interjection.27
  20. 20Panel: 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
  21. 21Guest: 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.44
  22. 22Panel.09
  23. 23Guest: 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.19
  24. 24Panel: 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?53
  25. 25Guest answers the question and mentions Selenium!39
  26. 26Panel: I like that approach.27
  27. 27Chuck: When you say integration test what do you mean?35
  28. 28Sentry.ioAdvertisement
  29. 29Chuck: How much do the tools matter?52
  30. 30Guest: The revolutions matter. Whether you use Jasmine or Mocha or whatever I don’t think it matters. The tests matter not the tools.01
  31. 31Aimee: Yes and no. I think some tools are outdated.39
  32. 32Guest: 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 the50
  33. 33Aimee: I am curious would you be willing to expand on what the Selenium folks were saying about Puppeteer and others may not provide?29
  34. 34Aimee mentions Cypress.54
  35. 35Guest: My guessing is that their priority is not there. I kind of agree with them.08
  36. 36Aimee: I think they are focusing on mobile more.21
  37. 37Guest: 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.24
  38. 38it can do everything.Guest: Selenium is a Swiss knife
  39. 39Chuck: I am thinking about different topics to talk about. I haven’t used Puppeteer. What’s that about?32
  40. 40Guest: Puppeteer is much more like Selenium . The reason why it’s great is b/c Puppeteer will always be Google Chrome.49
  41. 41Chuck: 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?42
  42. 42Guest.06
  43. 43Chuck: You run tests against production?30
  44. 44Guest: Don’t run tests against production...let me clarify!45
  45. 45Chuck.14
  46. 46Guest: When I am talking about integration testing in the backend...21
  47. 47Chuck asks a question.37
  48. 48Guest: I am constantly running between frontend and backend.47
  49. 49Chuck: 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?14
  50. 50Guest: Frontend is so visual.40
  51. 51Chuck: What are you working on now?12
  52. 52Guest: I am working with Applitools and I was impressed with what they were doing.16
  53. 53Guest: Those screenshots are never the same.08
  54. 54Panel: It’s...comparing the output to the static site to the...36
  55. 55Guest: I am working mostly (right now) in backend.28
  56. 56Chuck: Anything else? Picks!40
  57. 57Advertisement: Get A Coder Job!57

More from Gil

All sets

Similar sets

  • Andy BellJSJ 343: The Power of Progressive Enhancement with Andy Bell · 11 Dec 2018 · 1:05

About this set

57 tracks, from 00 – Advertisement: KENDO UI to 57 – Advertisement: Get A Coder Job!.

Added 21 Oct 2026

00:00
00:00 /