https://www.youtube.com/watch?v=RAxiiRPHS9k
At 40 prevent fear minute to minute, second to second (enable refactoring)
At 1:30 He refers to the extremely high level test as a testing-concept-system-tests
At 2:30 testing-concept-write-test-from-bottom-up
talk-fast-test-slow-test-gary-bernhardt#non-restful-url1 At 3:14 He uses very non-restful URL like "/markpostasspam, {postid: post.pk}" talk-fast-test-slow-test-gary-bernhardt#non-restful-url1
talk-fast-test-slow-test-gary-bernhardt#what-can-cause-to-break1 At 4:00 What are all the things that can cause the test to break? talk-fast-test-slow-test-gary-bernhardt#what-can-cause-to-break1
At 5:45 testing-concept-the-dangers-of-negative-assertions
talk-fast-test-slow-test-gary-bernhardt#binary-test-suite1 At 6:50 - the binary test suite. "It tends to completely succeed or completely fail. It doesn't give you any fine-grained feedback about what has actually gone wrong, it just tells you you broke something." talk-fast-test-slow-test-gary-bernhardt#binary-test-suite1
talk-fast-test-slow-test-gary-bernhardt#hard-to-test-edge-cases-from-the-outside1 At 8:00 - "It is very very difficult to test fine-grained edge cases and things like that from the outside. It's very difficult to set the world up in this complicated way where this very rare case is triggered." talk-fast-test-slow-test-gary-bernhardt#hard-to-test-edge-cases-from-the-outside1
Only on release-gating that things get fixed. (Liked the term release gating)
talk-fast-test-slow-test-gary-bernhardt#units-that-are-too-big-slow-down-superlinearly1 At 9:30 - Talks about unit tests that are too big. The time to run the same test grows superlinearly as all of the things it relies on slow down by getting bigger. talk-fast-test-slow-test-gary-bernhardt#units-that-are-too-big-slow-down-superlinearly1
At 10:50 - another way to fail is to write fine-grain tests around legacy code. Baking in the badness forever...
At 13 talks about his definition of a unit test, which is different from various other definitions
At 16:40 - "Why is this a unit test? ... First of all, this tests one object behavior, only."
At 14:05 - It is a unit test because other classes can't break it.
at 17:00 balance of 95% unit to 5% system on new systems, trending towards 99% system and 1% system as the system matures
At 19:00 web applications are object heavy systems without a lot of boundaries
At 20:30 how to test fast with db
testing-concept-test-fragility