Philippe Vaillancourt!
Senior Software Engineer at Taazaa
Bio!
Phil has so little experience as a software developer that it's not even worth mentioning. He has never written a book, doesn't have a course on Pluralsight and has helped trained a total of 5 junior developers and one dog. As you can tell, Phil has big time impostor syndrome. But Phil really, really likes writing software, reading about writing software and talking about writing software.
If you must know, he does have a blog (https://blog.snowfrog.dev), a YouTube channel, a podcast (https://podcast.snogwfrog.dev), some open source packages (https://www.npmjs.com/~snowfrog), a Twitter account (https://twitter.com/snowfrogdev), yaddi-yadda... but I still mostly think he's a fraud.
Session!
The Spy of Testadel: a unit-testing medieval tale
When people get started with unit testing, they often get stumped when it comes to testing functions that have side effects. This talk is a gentle introduction to some of the concepts involved in testing side effects.
The year is 1452. An uneasy truce between the kingdom of Testadel and the fiefdom of its neighbour, Sir SideEffects, is on the verge of collapse. Follow along as our hero, a court jester aptly named Jest, infiltrates the enemy's camp to gather information, and uncover Sir SideEffects' treachery.
Through the clever - I think - use of an allegory, this talk will answer:
- What is the difference between a pure function and a function with side-effects.
- Why testing functions with side-effects is usually harder.
- What strategies can be employed to test functions with side-effects, and their tradeoffs.
- What are spies and how to use them.
- What libraries can help with testing side-effects.
Where/When?