{ "uuid": [ { "value": "0a3bf034-7203-45c2-aae5-74f9211929fa" } ], "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:32+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": "What's the simplest test to begin with?\n" } ], "created": [ { "value": "2023-09-07T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:32+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2023\/09\/07\/what-s-the-simplest-test-to-begin-with", "langcode": "en" } ], "body": [ { "value": "\n
When giving talks and workshops or coaching on automated testing and test-driven development, some people may not have written tests before and aren't familiar with the structure or know where to begin.<\/p>\n\n
In the workshops I ran for DrupalCamp London and DrupalCamp NYC, I wanted to cover this first before writing any implementation code.<\/p>\n\n
Where do you put a test class, and what does it contain?<\/p>\n\n
How do you run the tests, and how can you make it pass or fail?<\/p>\n\n
To start, we wrote a test for existing functionality within Drupal core - anonymous users can visit the front page.<\/p>\n\n
This is the whole test:<\/p>\n\n
<?php\n\nnamespace Drupal\\Tests\\my_module\\Functional;\n\nuse Drupal\\Tests\\BrowserTestBase;\nuse Symfony\\Component\\HttpFoundation\\Response;\n\nclass MyModuleTest extends BrowserTestBase {\n\n\u00a0 protected $defaultTheme = 'stark';\n\n\u00a0 \/** @test *\/\n\u00a0 public function the_front_page_loads_for_anonymous_users() {\n\u00a0 \u00a0 $this->drupalGet('<front>');\n\n\u00a0 \u00a0 $this->assertResponse(Response::HTTP_OK);\n\u00a0 }\n\n}\n<\/code><\/pre>\n\nThis is a test someone can write, run and see the test pass.<\/p>\n\n
They can then experiment by changing the values to make the test fail in different ways.<\/p>\n\n
What next?<\/h2>\n\n
Then, we tested anonymous users cannot access the administration pages, which is also already the case in Drupal core, and then authenticated users with the correct permissions could access them.<\/p>\n\n
People were getting the idea by now, and we moved on to writing and testing some of our own code.<\/p>\n\n ",
"format": "full_html",
"processed": "\n
When giving talks and workshops or coaching on automated testing and test-driven development, some people may not have written tests before and aren't familiar with the structure or know where to begin.<\/p>\n\n
In the workshops I ran for DrupalCamp London and DrupalCamp NYC, I wanted to cover this first before writing any implementation code.<\/p>\n\n
Where do you put a test class, and what does it contain?<\/p>\n\n
How do you run the tests, and how can you make it pass or fail?<\/p>\n\n
What we did<\/h2>\n\n
To start, we wrote a test for existing functionality within Drupal core - anonymous users can visit the front page.<\/p>\n\n
This is the whole test:<\/p>\n\n
<?php\n\nnamespace Drupal\\Tests\\my_module\\Functional;\n\nuse Drupal\\Tests\\BrowserTestBase;\nuse Symfony\\Component\\HttpFoundation\\Response;\n\nclass MyModuleTest extends BrowserTestBase {\n\n protected $defaultTheme = 'stark';\n\n \/** @test *\/\n public function the_front_page_loads_for_anonymous_users() {\n $this->drupalGet('<front>');\n\n $this->assertResponse(Response::HTTP_OK);\n }\n\n}\n<\/code><\/pre>\n\nThis is a test someone can write, run and see the test pass.<\/p>\n\n
They can then experiment by changing the values to make the test fail in different ways.<\/p>\n\n
What next?<\/h2>\n\n
Then, we tested anonymous users cannot access the administration pages, which is also already the case in Drupal core, and then authenticated users with the correct permissions could access them.<\/p>\n\n
People were getting the idea by now, and we moved on to writing and testing some of our own code.<\/p>\n\n ",
"summary": null
}
]
}