{ "uuid": [ { "value": "d783263e-b457-4785-b15c-ce631faf3192" } ], "langcode": [ { "value": "en" } ], "type": [ { "target_id": "daily_email", "target_type": "node_type", "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7" } ], "revision_timestamp": [ { "value": "2025-05-11T09:00:38+00:00" } ], "revision_uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "revision_log": [], "status": [ { "value": true } ], "uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "title": [ { "value": "Once you start writing tests, you can't stop\n" } ], "created": [ { "value": "2023-07-01T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:38+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2023\/07\/01\/once-you-start-writing-tests-you-cant-stop", "langcode": "en" } ], "body": [ { "value": "\n
Once you start testing\/TDD, you can't go back<\/p>\n\n
Once you start writing automated tests or doing test-driven development, you can't go back to not doing it.<\/p>\n\n
When adding a new feature, you'd need to test every situation and use case manually in a browser or command line - and, very likely, do so multiple times.<\/p>\n\n
When fixing a bug, you'd need to follow the exact steps to replicate it and see it before attempting a fix. Again, you'd also need to test it manually.<\/p>\n\n
Also, because it passes a manual test, there's no guarantee it won't break unexpectedly in the future.<\/p>\n\n
While refactoring code without tests, bugs and regressions could be introduced as there's no test suite to run and ensure they're still passing.<\/p>\n\n
When you're used to writing tests and doing test-driven development, you get used to the quick feedback loops and the confidence to make changes.<\/p>\n\n
It's easier to create a test that proves a bug exists and shows it'safixed because the test passes.<\/p>\n\n
Once you have these things, you can't stop and go back to not having tests.<\/p>\n\n ", "format": "full_html", "processed": "\n
Once you start testing\/TDD, you can't go back<\/p>\n\n
Once you start writing automated tests or doing test-driven development, you can't go back to not doing it.<\/p>\n\n
When adding a new feature, you'd need to test every situation and use case manually in a browser or command line - and, very likely, do so multiple times.<\/p>\n\n
When fixing a bug, you'd need to follow the exact steps to replicate it and see it before attempting a fix. Again, you'd also need to test it manually.<\/p>\n\n
Also, because it passes a manual test, there's no guarantee it won't break unexpectedly in the future.<\/p>\n\n
While refactoring code without tests, bugs and regressions could be introduced as there's no test suite to run and ensure they're still passing.<\/p>\n\n
When you're used to writing tests and doing test-driven development, you get used to the quick feedback loops and the confidence to make changes.<\/p>\n\n
It's easier to create a test that proves a bug exists and shows it'safixed because the test passes.<\/p>\n\n
Once you have these things, you can't stop and go back to not having tests.<\/p>\n\n ", "summary": null } ], "feeds_item": [ { "imported": "1970-01-01T00:33:45+00:00", "guid": null, "hash": "fb71e18ebe99ec55d0c2fe23152a48ed", "target_type": "feeds_feed", "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76" } ] }