From a9fafe159927a591276a25736130865cdb015de5 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 12 Oct 2023 00:31:45 +0100 Subject: [PATCH] daily-email: add 2023-10-08 Is test-driven development difficult? --- src/content/daily-email/2023-10-08.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 src/content/daily-email/2023-10-08.md diff --git a/src/content/daily-email/2023-10-08.md b/src/content/daily-email/2023-10-08.md new file mode 100644 index 00000000..56bab954 --- /dev/null +++ b/src/content/daily-email/2023-10-08.md @@ -0,0 +1,25 @@ +--- +title: > + Is test-driven development difficult? +pubDate: 2023-10-08 +permalink: > + archive/2023/10/08/is-test-driven-development-difficult +tags: + - software-development + - automated-testing + - test-driven-development + - continuous-integration + - trunk-based-development +--- + +I recently read a post where the writer said automated testing, test-driven development, continuous integration, trunk-based development, etc, are difficult. + +I'm familiar with them and have been using them for some time, but I think trunk-based development is easier as there's only a single branch instead of many. + +Continuous integration is pulling everyone else's code at least once daily and pushing yours to ensure it doesn't conflict. + +Test-driven development is writing failing tests before any implementation code and refactoring once it passes. + +I don't think these are technically difficult, but they do require an open mind, a willingness to learn, evaluate and consider alternative approaches and, in some cases, change existing behaviour. + +Change can be the difficult part, not which brand you commit to, how often you push your code or when you write your tests.