By now hopefully most of the developers know tests are worth writing. Unfortunately, sometimes their quality leaves a lot to be desired. Tests produced are tightly coupled, testing wrong things with wrong set of assertions.
There are many discussions addressing the questions like "What to test" and "How to test". But there is one equally important - "How to write test someone else can read". While there is no tool on the world that would do the former for you, the latter can be vastly improved with right set of techniques, tricks and libraries. If we are committing to writing tests, we might as well get the most of it.
That is what this talk will be about: ideas and patterns to produce clean, readable and developer-friendly tests. We will look deep into technical details, some of which include: patterns for building your test objects, prettifying test output or defining descriptive assertions.
YOU MAY ALSO LIKE:
- Going Interactive with Visual Studio 2015 (SkillsCast recorded in June 2016)
- Janet Gregory's Agile Testing for the Whole Team (in London on 28th - 30th October 2019)
- Uncle Bob Martin's Clean Code Workshop on Agile Software Craftsmanship (in London on 2nd - 3rd December 2019)
- droidcon London 2019 (in London on 24th - 25th October 2019)
- P3X - People, Product & Process eXchange 2019 (in London on 31st October - 1st November 2019)
- Testing and UB (in London on 21st November 2019)
- Testing in Production. From DevTestOops to DevTestOps (SkillsCast recorded in September 2019)
- Keynote: Is DevOps Still Relevant In A Cloud Native World? (Enterprise Edition) (SkillsCast recorded in September 2019)
A swiss army knife for readable tests
Adam is a software developer at PayPoint, journeyman on objective, functional, mobile and any other code worth writing. Keenly interested in principles behind programming and curious why people do what they do and write code they write.