When using the Mail facade in Laravel it is not so easy to test the output of the parsed mail template. Like http://stackoverflow.com/questions/31120567/unittesting-laravel-5-mail-using-mock I received the error Method Mockery_0__vendor_Swift_Mailer::getTransport() does not exist on this mock object. I ended up in listening to the mailer.sending event: public function testRegistrationMailIsSend_afterSubmittingForm() { // […] The post Integration testing the mail dispatching in Laravel…
#laravel
5 posts
1 Aug 2015
28 Jul 2015
In my last post I wrote about how to define the test environment for database integration tests. Now I want to describe, how the database can be populated with test or stam data. First of all, every test inherited from the generated TestCase class executes the Artisan migrate command (TestCase::prepareForTests()). […] The post Seeding the database for integration tests in…
27 Jul 2015
As far as I have read, in Laravel 4 you could define your database integration test environment by adding a testing/database.php or .env.testing.php file containing your configuiration. In Laravel 5 both ways does no longer work. To switch your environment you have two options: Put both configuration definitions (testing, dev/production) […] The post Test environments for database integration tests in…
25 Jul 2015
This post highlights 6 important rules to keep in mind when developing performant web applications: avoid premature optimization, do the minimum required work, defer non-critical tasks, leverage caching, avoid N+1 queries, and design for horizontal scaling. Following these guidelines will help you write efficient code from the start and build apps ready to handle growth.
18 Apr 2015
This tutorial shows step-by-step how to bootstrap a Lumen project, configure MySQL, create migrations and models, seed the database, define routes and templates to build a fully working motivational quote web app in less than 30 minutes.