oliverdavies.uk/content/node.9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c.json

91 lines
4.3 KiB
JSON
Raw Normal View History

2025-05-11 07:15:45 +01:00
{
"uuid": [
{
2025-05-11 09:40:11 +01:00
"value": "9aeee1e5-7b2c-4ce8-b034-ecd7531edf7c"
2025-05-11 07:15:45 +01:00
}
],
"langcode": [
{
"value": "en"
}
],
"type": [
{
"target_id": "daily_email",
"target_type": "node_type",
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
}
],
"revision_timestamp": [
{
2025-05-11 09:40:11 +01:00
"value": "2025-05-11T09:00:05+00:00"
2025-05-11 07:15:45 +01: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": "How would you write this test name?"
}
],
"created": [
{
"value": "2024-10-22T00:00:00+00:00"
}
],
"changed": [
{
2025-05-11 09:40:11 +01:00
"value": "2025-05-11T09:00:05+00:00"
2025-05-11 07:15:45 +01:00
}
],
"promote": [
{
"value": false
}
],
"sticky": [
{
"value": false
}
],
"default_langcode": [
{
"value": true
}
],
"revision_translation_affected": [
{
"value": true
}
],
"path": [
{
"alias": "\/daily\/2024\/10\/22\/how-would-you-write-this-test-name",
"langcode": "en"
}
],
"body": [
{
"value": "\n <p>There are multiple ways I've seen people write their test method names.<\/p>\n\n<p>This is the standard PSR-compliant camel-case method name:<\/p>\n\n<pre><code class=\"php\">public function testSomethingHappensWhenYouGoToThePage()\n<\/code><\/pre>\n\n<p>Some people find long camel-case names hard to read and prefer to use snake-case names:<\/p>\n\n<pre><code class=\"php\">public function test_something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>This still works as the method name still starts with the word <code>test<\/code>, but you'd need to add some overrides to phpcs for it not to complain about using snake-case words.<\/p>\n\n<p>Another option is to remove the <code>test<\/code> prefix and use an annotation:<\/p>\n\n<pre><code class=\"php\">\/** @test *\/\npublic function something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>And in newer PHPUnit versions, you can also use an attribute:<\/p>\n\n<pre><code class=\"php\">#[Test]\npublic function something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>Whilst this makes the method name shorter, you need to add an additional line before each test method for the annotation or attribute.<\/p>\n\n<p>Each has pros and cons, and people have their own preferences.<\/p>\n\n<p>Which do you do?<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>There are multiple ways I've seen people write their test method names.<\/p>\n\n<p>This is the standard PSR-compliant camel-case method name:<\/p>\n\n<pre><code class=\"php\">public function testSomethingHappensWhenYouGoToThePage()\n<\/code><\/pre>\n\n<p>Some people find long camel-case names hard to read and prefer to use snake-case names:<\/p>\n\n<pre><code class=\"php\">public function test_something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>This still works as the method name still starts with the word <code>test<\/code>, but you'd need to add some overrides to phpcs for it not to complain about using snake-case words.<\/p>\n\n<p>Another option is to remove the <code>test<\/code> prefix and use an annotation:<\/p>\n\n<pre><code class=\"php\">\/** @test *\/\npublic function something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>And in newer PHPUnit versions, you can also use an attribute:<\/p>\n\n<pre><code class=\"php\">#[Test]\npublic function something_happens_when_you_go_to_the_page()\n<\/code><\/pre>\n\n<p>Whilst this makes the method name shorter, you need to add an additional line before each test method for the annotation or attribute.<\/p>\n\n<p>Each has pros and cons, and people have their own preferences.<\/p>\n\n<p>Which do you do?<\/p>\n\n ",
"summary": null
}
]
}