Sean and Sam talk all about testing. Sam created an ideal testing pyramid based on personal experience and from talking with test thought leaders, such as Justin Searls. The testing pyramid has “integrated” at the top, and “isolated/unit” at the bottom, along with a wide base and X axis for the number of tests you should be writing. Write as few integration tests as possible, although you may write some that you don’t keep. Isolated tests refer to where the only thing you are executing is one file or function’s worth of code. Then, there’s some tests to never write. You should be able to look at a test and know instantly if it’s correct or not. Whether using a pyramid or bowtie scheme, teams should embrace testing, rather than hate it.
📆 2018-10-23 23:25 / ⌛ 00:34:23
📆 2018-10-12 01:38 / ⌛ 00:37:04
📆 2018-10-05 02:49 / ⌛ 00:42:58
📆 2018-09-28 13:49 / ⌛ 00:38:44
📆 2018-09-20 23:00 / ⌛ 00:36:00