From c08cff9f799c2c694526886402af5acfe21a8705 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 1 Feb 2024 21:46:17 +0000 Subject: [PATCH] Add daily email for 2024-01-31 Automated tests mean you can make changes quicker --- source/_daily_emails/2024-01-31.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 source/_daily_emails/2024-01-31.md diff --git a/source/_daily_emails/2024-01-31.md b/source/_daily_emails/2024-01-31.md new file mode 100644 index 00000000..0dc2fa31 --- /dev/null +++ b/source/_daily_emails/2024-01-31.md @@ -0,0 +1,25 @@ +--- +title: Automated tests mean you can make changes quicker +date: 2024-01-31 +permalink: archive/2024/01/31/automated-tests-mean-you-can-make-changes-quicker +snippet: | + Automated tests mean you can make changes quicker and not worry about introducing regressions. +tags: + - software-development + - automated-testing + - test-driven-development +--- + +Before fixing [yesterday's bug][yesterday], because I'd written automated tests, I ran them to ensure they were all passing. + +Then, I was able to focus solely on adding the new use case - starting with a failing test to replicate the issue and then getting it to pass. + +Because it was already tested, I didn't need to worry about breaking any other functionality and introducing regressions. + +When the new test was passing, I could run the whole test suite and ensure they still passed and things continued to work. + +Without the tests, I'd either need to check everything else manually (which takes time) or worry that something could potentially be broken. + +Having tests meant I could be confident that the new and existing functionality worked. + +[yesterday]: {{site.url}}/archive/2024/01/30/tdd-doesnt-mean-you-know-everything-upfront