You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer
I want to be able to identify the transport by the transport key/name used to send an email in my test
In order to ensure the mail was sent with the selected transport
Example
Given the following mailer configuration with multiple transports:
As of now, I cannot write a functional test to test that the expected transport is used. The transport is not identified by the declared transport key (i.e sendmail, brevo, other_brevo) but instead the transport in events is the transport casted as a string.
self::assertEmailCount(1, 'brevo'); // failsself::assertEmailCount(1, 'null://'); // pass but is it brevo or sendmail or other_brevo as both use null transport in test env ?self::assertEmailCount(1, 'brevo+api://api.brevo.com'); // pass if I use brevo transport but it will call the API and I don't know if it's brevo or other_brevo
As X-Transport is removed from the message, I cannot assert on the header.
The text was updated successfully, but these errors were encountered:
Description
As a developer
I want to be able to identify the transport by the transport key/name used to send an email in my test
In order to ensure the mail was sent with the selected transport
Example
Given the following mailer configuration with multiple transports:
I have some code that will set the header X-Transport with the target transport to use :
As of now, I cannot write a functional test to test that the expected transport is used. The transport is not identified by the declared transport key (i.e
sendmail
,brevo
,other_brevo
) but instead the transport in events is the transport casted as a string.As X-Transport is removed from the message, I cannot assert on the header.
The text was updated successfully, but these errors were encountered: