We all know that writing tests for our code is “what we should do”, and maybe we’re even doing that already. But it feels like extra busy-work that slows us down – and they hardly ever catch any bugs anyway…
Maybe we’ve even tried TDD, and felt that it was just adding even more ceremony to the problem with no real advantages.
But the advantages are definitely there! We just need a good grounding in what TDD actually is (and isn’t) and how to do it properly – especially in the context of C++, which brings it’s own idiosyncrasies and bottlenecks to the matter.
That’s what this workshop aims to be. Whether you’ve never written a test before, or you’ve had some mileage with TDD already, be prepared to ratchet up your productivity by thinking about things in new ways and gaining more approaches to breaking down problems in sustainable ways.
* Types and roles of tests.
* What is a test?
* How to write good tests (and avoid writing bad ones).
* What are the benefits of writing tests first?
* The TDD cycle
* The art and craft of TDD
* The psychology of TDD and maximising mental flow states
* How TDD slows you down
* How TDD makes you go faster!
* The transformation priority premise
Время: 10:00 - 19:00 (GMT+3)
350 BYN (до 31.03.2021)
400 BYN (до 30.04.2021)
Developer Advocate, JetBrains, UK
Phil is the author of the test frameworks Catch for C++ and Objective-C, and Swordfish for Swift. As Developer Advocate at JetBrains he's involved with CLion, AppCode and ReSharper C++. …