JS Unit Testing Good Practices & Horrible Mistakes • Roy Osherove • GOTO 2013

[@monugupta32]

The frustration in the talk is real.

[@lancerkind]

Roy, great talk! Loved it all!

[@joynalabedin2875]

Amazing talk!

[@gunelismayilova9854]

why is there no tool to check unit test quality :(

[@rodolfoyanez3452]

There are mutation test tools that can give You a hint of how strong are your tests, it is not 100%effective but it is a help

[@Vlfkfnejisjejrjtjrie]

Hahaha..the intro was good,"good practices and possible mistakes". Coding Snowflakes.

[@nicholasaurus]

Unit Tests == People who have given up on life and are looking for more excuses to site behind a computer and belittle everyone else. || People who gave up on software development and now just want to write tests and not worry about implementation || Missed opportunity to be writing software that makes money while your competition is adding features || Blowing up the thing things that don't matter in life to the largest possible format || Solidifying anything in a world where the only constant is change. A better answer is letting the world be your unit test. Fix it when it breaks. You cannot predict everything. Do end to end tests. Testing a method, like a cell outside of it's body tells you nothing about the whole product functioning, which the only thing that matters. We write code to solve real life problems, not to write code.

[@coolsebz]

nicholasaurus ===* you would've caught that if you wrote some basic tests

[@nicholasaurus]

coolsebz They are not exactly the same. so I mean ==

[@coolsebz]

Judging from how condescending you were and how you expressed yourself, your comment showed a direct equality between the two. If you don't want to come across as an ignorant, you should be a bit more careful to how you say things. And this is strictly regarding the way you wrote your message, not its content. That's a story for another day.

[@nicolal.1171]

+nicholasaurus you are a master in excel I think...

[@CaptainCarthex]

+nicholasaurus Microsoft did a study and found that teams that use TDD take ~30% longer to finish projects BUT have ~90% less bugs after release. You can't let the world be your unit test in a corporate environment, if things continually break in production then your clients aren't going to want to use your products anymore. Also, you don't add unit tests at the expense of full end-to-end tests, you need both.