91 lines
No EOL
3.2 KiB
JSON
91 lines
No EOL
3.2 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "defbeab8-28ca-4444-b09b-5121de794602"
|
|
}
|
|
],
|
|
"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:05+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": "Keep your test suite passing"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-11-05T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:05+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/11\/05\/keep-your-test-suite-passing",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>I once joined a project that had some automated tests and quality checks which were run automatically in a CI pipeline whenever code was pushed.<\/p>\n\n<p>The problem was that one of the checks were failing which caused the pipeline to fail.<\/p>\n\n<p>Because it was failing, it was ignored.<\/p>\n\n<p>But if it's already failing and being ignored, how do you know you haven't broken something unexpectedly?<\/p>\n\n<p>This is the value you get from automated tests that are run regularly, but if failures are being ignored, they aren't adding value or confidence the code works.<\/p>\n\n<p>In the end, it was a small fix to get the tests and CI pipeline passing again and we made sure to keep it passing as much as possible once it was.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>I once joined a project that had some automated tests and quality checks which were run automatically in a CI pipeline whenever code was pushed.<\/p>\n\n<p>The problem was that one of the checks were failing which caused the pipeline to fail.<\/p>\n\n<p>Because it was failing, it was ignored.<\/p>\n\n<p>But if it's already failing and being ignored, how do you know you haven't broken something unexpectedly?<\/p>\n\n<p>This is the value you get from automated tests that are run regularly, but if failures are being ignored, they aren't adding value or confidence the code works.<\/p>\n\n<p>In the end, it was a small fix to get the tests and CI pipeline passing again and we made sure to keep it passing as much as possible once it was.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |