This presentation show a nice way, how emails in Symfony can be sent - and - how everything can be tested in a cool way that makes much more fun than writing functional tests in Symfony

1. Sending and Testing
Mails in Symfony
Christoph Hautzinger
@chautzi // christoph-hautzinger.de
#webdevbbq, 09.06.2015

2. @chautzi - hugh!?
• Webdev half of my live!
• Symfony 9 years
• diginights
• Fressnapf
• wetter.com
• ampya.com
• *.conspecton.com
• @conspecton Founder
• looking for a job? ;)
• Freelancing

4. Sending Mails

5. Status Quo
http://symfony.com/doc/current/cookbook/email/email.html

6. Disadvantages
• All parts of the mail reside in different places
• I18N?
• Code duplication
• Tight coupling
• 20 LOC!?

7. HautziSystemMailBundle
https://packagist.org/packages/hautzi/system-mail-bundle
https://github.com/christoph-hautzinger/SystemMailBundle
http://knpbundles.com/christoph-hautzinger/SystemMailBundle

8. How to use?

9. Additional stuff :-)

10. DDD Approach
thanks for the code!

11. Testing Mails

12. Status Quo
• Unit Tests
• In your domain, mock interfaces
• Functional Tests
• the profiler knows everything (when enabled)
• but writing functional tests in Symfony is not fun!

13. codeception
http://codeception.com/

14. mailcatcher
http://mailcatcher.me/
• provides simple smtp mail server
• default smtp://127.0.0.1:1025
• exposes simple mailclient gui
• default http://127.0.0.1:1080
• REST API to control everything
• http://127.0.0.1:1025
$ gem install mailcatcher
$ mailcatcher --ip=0.0.0.0

16. configuring Symfony
also very useful in dev environment!

17. combine
codeception and mailcatcher
https://github.com/captbaritone/codeception-mailcatcher-module

18. Thank you!
Q&A
@chautzi
Slides available at http://christoph-hautzinger.de