Friday 14.10-15.00

Add this session to your schedule

Imagine you are a evil developer and you want to write hard to test code. What do you do? Would you declare everything private? Put everything in one big method? Give nondescript names? Turns out none of that is hard to test, but some things which we do every day are. Will writing tests cost you double the development time? How can writing more code be faster? Is testing really just for QA? Find these answers and more at psychology of testing talk.