{ "uuid": [ { "value": "7989ae69-0f6d-4a7d-b560-d828f76cfba4" } ], "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:06+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": "Is testing a chore?" } ], "created": [ { "value": "2024-09-29T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:06+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2024\/09\/29\/is-testing-a-chore", "langcode": "en" } ], "body": [ { "value": "\n

Do some Developers skip writing tests for their personal projects<\/a> because they think it's a chore?<\/p>\n\n

If they've written the code, so they then think it's too much work to write tests or need to move on to the next task?<\/p>\n\n

Is it boring to write tests for code that's already written and will pass straight away?<\/p>\n\n

This is why I do test-driven development and start with a failing test and then write code to make it pass.<\/p>\n\n

Then, I add more to the test until it fails and then get that to pass.<\/p>\n\n

When that test is finished, I'll move to a new test for a different piece of functionality.<\/p>\n\n

I like this approach of working in small feedback cycles and alternating between failing and passing tests.<\/p>\n\n

Testing this way isn't boring or a chore and much more interesting for me compared to writing all the code first and maybe writing the tests later.<\/p>\n\n ", "format": "full_html", "processed": "\n

Do some Developers skip writing tests for their personal projects<\/a> because they think it's a chore?<\/p>\n\n

If they've written the code, so they then think it's too much work to write tests or need to move on to the next task?<\/p>\n\n

Is it boring to write tests for code that's already written and will pass straight away?<\/p>\n\n

This is why I do test-driven development and start with a failing test and then write code to make it pass.<\/p>\n\n

Then, I add more to the test until it fails and then get that to pass.<\/p>\n\n

When that test is finished, I'll move to a new test for a different piece of functionality.<\/p>\n\n

I like this approach of working in small feedback cycles and alternating between failing and passing tests.<\/p>\n\n

Testing this way isn't boring or a chore and much more interesting for me compared to writing all the code first and maybe writing the tests later.<\/p>\n\n ", "summary": null } ], "feeds_item": [ { "imported": "1970-01-01T00:33:45+00:00", "guid": null, "hash": "4b2d47376db0c887f15bedf49de35711", "target_type": "feeds_feed", "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76" } ] }