Everytime we make a test we are trading time for information. Let's take a look at some of the criteria which may help us decide when and how to invest in a test, when it's worth automating, and what are some of the key factors to take into account to decide when it's a good time to stop testing (an activity we could be doing forever).
(hint: criterias will include
maintainability, execution time, cognitive load, risk we want to prevent, prevention vs. mitigation, leading vs lagging information, AB testing, amount of impact in users (traffic x value of the feature), refactoring friendliness (TDD), knowledge in the world VS. knowledge in the head, ...)
Presenter: Xavi Ametller Serrat
Moderator: Luc van Vugt
00:04:34 - Introduction Xavi / Test are bets
00:05:22 - My first experience with automated testing
00:08:57 - When do I stop testing?
00:12:33 - The value of a test
-- 00:24:25 - Number of executions
-- 00:25:05 - Usage of the feature
-- 00:25:42 - Are we testing the right thing?
-- 00:26:45 - Feature complexity/criticality
-- 00:28:18 - Future refactors backed by the test
-- 00:29:07 - When do we cerate the test / test after vs. TDD
-- 00:30:17 - The moment we recieve the feedback
00:32:44 - All about the future... (and some Q & A)
00:43:03 - Let's play some models
-- 00:43:21 - So .. when to test?
-- 00:50:24 - When to stop testing?
-- 00:56:55 - Tech practices
-- 00:58:38 - No Tests, Test After or TDD
-- 01:00:00 - From Pyramid to other shapes
01:01:30 - And now what?
01:01:43 - You can measure the outcome of your bets
01:02:57 - Summary
01:03:37 - Q & A