uuid: - value: da3412f8-9a33-4395-a75e-4d107d2557a4 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:34+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: | Writing custom assertions in your tests created: - value: '2023-08-17T00:00:00+00:00' changed: - value: '2025-05-11T09:00:34+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2023/08/17/writing-custom-assertions-in-your-tests langcode: en body: - value: |
Writing custom assertions is a great way to clean up your test code.
Here's an example from one of my client Drupal projects:
private static function assertProductVariationHasPrice(ProductVariationInterface $productVariation, string $expectedPrice): void {
self::assertSame(
actual: $productVariation->getPrice()->getNumber(),
expected: $expectedPrice,
);
}
This one wraps a single assertion, but they could also include multiple assertions or additional steps.
A custom assertion is a simple function but it makes the test code more readable and less repetitive.
format: full_html processed: |Writing custom assertions is a great way to clean up your test code.
Here's an example from one of my client Drupal projects:
private static function assertProductVariationHasPrice(ProductVariationInterface $productVariation, string $expectedPrice): void {
self::assertSame(
actual: $productVariation->getPrice()->getNumber(),
expected: $expectedPrice,
);
}
This one wraps a single assertion, but they could also include multiple assertions or additional steps.
A custom assertion is a simple function but it makes the test code more readable and less repetitive.
summary: null field_daily_email_cta: { }