No BS TS #31 - Testing with Jest and Wallaby

[@Papapiishu]

I'd love to see something about writing tests for React components

[@jherr]

Agreed. I'll add that to the list.

[@mainendra]

me too

[@victorlongon]

@@jherr maybe have a video with react testing library and typescript?

[@ThEldeRS]

One of the best productivity boosters I've ever seen! LOVE your channel and this series!

[@shashydass4114]

Great video. I think the no BS TS series is essential viewing for Typescript developers. Just incredible content!

[@francis_n]

My company has just bought us Wallaby licenses and once you go Wallaby there is no way you can go back to the terminal. Such a productivity boster!

[@jherr]

Big time! It's spectacular for library development in particular.

[@AAquaticAApe]

wow for Wallaby! thanks for sharing this awesome extension!

[@babyboie20]

Thanks a million for the sort of quick start guide!

[@MichaelCampbell01]

Thanks, this helped a lot with a new express/typescript/jest project. And never heard about Wallaby, so that's cool too.

[@Bill-cw1ei]

Wallaby is a great time saver, thanks for letting us know!

[@align2source]

Awesome series! Love the vibe of it all, and just really great content 💚

[@jackh3242]

I had to use jest/enzyme for a React project at school. Such a pain in the butt. :/ I'm looking forward to your video about testing React components!

[@ryanjensen4232]

Awesome, thanks!

[@EnLaMitad]

I love your channel Jack. Keep the amazing content coming.

[@thefonsotube]

I have no idea what you arte type in the terminal @1:40 to @3:10. What command are you entering to run ts-jest? By the way,,THANK YOU for putting all this together. Your hard work is MUCH appreciated!

[@Poopuupoo]

Pretty sure he is using the run from Run|Debug... but I can't figure out how he got those functions in the test in the first place!

[@user-gm3lg8gp3m]

thank you so much

[@dinoscheidt]

Just came here randomly to look up wallaby. But i wonder if yarn is still necessary since npm has adopted lock etc as well. At least that is the reason why I used it way back. Any reason why you prefer yarn over npm nowadays? (Honest question) ❤️ from Berlin

[@jherr]

The two leapfrog features over time, yarn jumped ahead with workspaces there for a bit, and then npm added support. So now it's more of a coin toss for me and I use yarn mostly out of habit.

[@ajaydwarkani]

@Jack Harrington, I like all your "No BS TS" videos. Thanks for spreading the knowledge. Can you share how do you get the inline "Run | Debug" option to run the script right from the editor?

[@jherr]

I think in this video that was powered by Wallaby.

[@ajaydwarkani]

​@@jherr I found this VS Code extension called "Jest Runner", that adds inline "Run | Debug" :)

[@victorlongon]

I have worked in pretty big projects and wallaby just was not up to the task. It is an awesome tool and it works great on smaller projects but once you use in big ones it just hangs itself and everything gets laggy in vs code. I had to stop using unfortunately (that was a couple of years a go not sure how it is nowadays). I have tests running in watch mode in parallel while I code. I usually use watch typ ahead for jest so i filter the tests I want to be running (so I don't run all tests)

[@jherr]

Yeah, when I use it for libraries it feels like it would get unresponsive on large projects with complex tests.

[@dmitryutkin9864]

Thanx!

[@SARANSASIDHARAN1]

Thank you!

[@SCALENE5]

ty

[@nayeembadhusha4759]

Hey jack. I was looking for this and i love it

[@sashaikevich]

What’s your vscode theme? I like it

[@jherr]

Night Wolf [black]

[@lawrencejones51]

Wallaby seems to be a productivity enhancing tool. Can't wait to try it out.

[@ddikodroid]

love this series

[@stefanahlander871]

Good stuff!! 🙂

[@pekwind]

wow wow wow.

[@360nickx]

Wallaby is 🤯

[@saidkorseir192]

super 👍

[@denilsoncosta9837]

i'd like to see ts-jest with Next.js

[@nayeembadhusha4759]

Can u make a video on different remoteType or library type with module federation Like for example : remoteType:"module" or library:{type:'module',name:Header'} I dont want to expose my federated modules as globals or as an window object

[@jherr]

I'll definitely get back into Module Federation sometime soon and I'll add this to the list of topics.

[@8bits292]

Code link is wrong. The files are not there and there is no Episode 31 between the folders

[@berkaygurcan141]

I did not have the run and debug buttons, what can I do inside it?

[@ajaydwarkani]

If you have not already found it then the VS Code Extension is called "Jest Runner", that adds inline "Run | Debug" :) marketplace.visualstudio.com/items?itemName=firsttris.vscode-jest-runner

[@berkaygurcan141]

@@ajaydwarkani thank you

[@sairaj5660]

I expected this ❤️

[@juniovitorino]

Wallaby and Quokka have the same purposes?

[@jherr]

Quokka is like a notepad with real-time execution of the code.

[@victorlongon]

Wallaby is built on top of quokka if I am not mistaken

[@victorlongon]

@@jherr do you use wallaby in real big projects nowadays? We had licences and everything on a previous workplace but wallaby was just not up to the task with real big things. Maybe the have changed that now? It is a fantastic tool, but it has to work in real projects so we can use on a daily basis

[@jherr]

@@victorlongon If I'm writing a library then I use it. In day-to-day UI work, not so much.

[@victorlongon]

@@jherr yeap, i might give a try on a components lib we have (not so big of a project).