))
Episode 31 - How (and why) to optimize your unit tests for performance?
Manage episode 437464737 series 3546970
Sisällön tarjoaa Fernando Doglio. Fernando Doglio tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.
Unit tests are usually 2nd (if not 3rd) class citizens in any codebase, teams usually work on them only once they're done with all the "important" features.
However, if you do it like that, chances are those tests will eventually start slowing your development process down. They will affect your coding, and your deployment pipelines, affecting your time-to-resolution metrics or even the business by slowing down time-to-market numbers.
In other words, bad tests are a real problem.
In this episode I cover several reasons why optimizing for performance is actually a great idea, and multiple things you can do to improve your unit tests.
Mainly:
- Get rid of your 3rd party dependencies.
- Test only what needs to be tested.
- Optimize the test data.
- Implement selective testing.
Get in touch!
- X (Twitter): https://twitter.com/deleteman123
- YouTube: https://www.youtube.com/@the-scripting-den
- My newsletter: https://fernandodoglio.substack.com/
Rate us!
To ensure the podcast reaches more developers, make sure to rate it on your favorite podcasting app and in Podchaser!
Thank you
36 jaksoa
Jaa
