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

preview_player
Показать описание
This presentation was recorded at GOTO Aarhus 2013. #gotocon #gotoaar

Roy Osherove - Senior consultant at ITVerket AS

ABSTRACT

RECOMMENDED BOOKS

#JavaScript #JS #unittesting

Looking for a unique learning experience?
Рекомендации по теме
Комментарии
Автор

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

gunelismayilova
Автор

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

Vlfkfnejisjejrjtjrie
Автор

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.

nicholasaurus