Hillel Wayne - Beyond Unit Tests: Taking Your Testing to the Next Level - PyCon 2018 on HackerTube: recommended by 3 Hacker News commenters across 3 separate months, 2018–2023.
talk · intermediate · evergreen
Hillel Wayne's PyCon 2018 talk on testing beyond pytest and mypy. It introduces property-based testing with the Hypothesis library and design-by-contract with dpcontracts, and shows how to combine them with an existing test suite.
HN commenters point to it as a concise, convincing case for better testing practice short of full formal methods.
“I found this talk (by the same person being interviewed) to be concise and convincing on how to do better than typical practice”
3 Hacker News comments link this video. Each one links back to its thread.
I found this talk (by the same person being interviewed) to be concise and convincing on how to do better than typical practice, without going to full formal methods. Hillel Wayne - Beyond Unit Tests: Taking Your Testing to the Next Level - PyCon 2018 ▶ this video
in “The Case for Formal Methods” · View on HN
Most of the non-joyful experience of writing tests lies in the context preparation, not so much in the expected outputs. I think we need a modern version of design by contract instead. Its one of the most powerful techniques of testing software is unfortunately often ignored and overlooked these days... Some less known things about design by contract: - you can easily test way more than types in preconditions and postconditions - extreme web controller postcondition example: every time there is a 200 response to a POST /new request, there should be at least one document more in storage than there was before the request. (caveat: unless there are deletes - then sum the deletes up too) - things important to the business look a ton like contracts - e.g. a diff of two legal documents always contains the full content (list of words) of both documents (never accidentally swallow content!) - your postconditions can surprisingly often fully describe the desired function behavior - with sufficient amount of pre and postconditions, your property tests look like "exercise the module or entire system with random actions" -> unit and integration tests (see Hilel Wayne's excellent video on this topic ▶ this video ) Some things that could really help modernize design by contract - Test at a certain sampling rate in production for expensive contracts (do not turn them off) - Report contract violations via observability mechanisms (tracing, sentry etc) - Better language support for contract DSLs
in “What if writing tests was a joyful experience?” · View on HN
Some of my favorite talks from Strange Loop: * Contracts For Getting More Programs Less Wrong: [link] * "It's Just Matrix Multiplication": Notation for Weaving: [link] * Hackett: a metaprogrammable Haskell: [link] * Git from the Ground Up: [link] From PyCon: * Beyond Unit Tests: Taking Your Testing to the Next Level: ▶ this video * Dataclasses: The code generator to end all code generator: [link] * Automating Code Quality: [link] There are probably more I might add later as I remember them.
in “Ask HN: Best talks of 2018?” · View on HN