Yes, you know, you should have written that test! But what If you already do writing tests, but you don't see the result of your actions. Tests run slow, they are fragile, hard to read and maintain. Fixing a test is harder than disabling it.

Don't blame yourself. It's not about you, it's about some points you should have taken into account while your testing codebase grew. In this talk I will tell you about
- What are best practices for tests (with code samples)
- Do we need acceptance tests and what framework to choose: Behat, Codeception, Selenium, PhantomJS
- How data should be managed? (Dumps, Fixtures, FactoryMuffin)
- How to test APIs (Codeception, php-vcr)
- Creating test environments with Docker containers
- Setting up parallel testing with Docker


Comments are closed.

Peter Fisher at 19:04 on 28 May 2017

A very thorough and well structured talk.

Great talk with very good tips when to use different type of testing.

A heard some interesting perspectives and ideas here, so it was useful talk.

Had a problem with understanding him well, but there was a lots of good tips

In first few minutes I had problem understanding Michael, but after that you just get used to his pronounciation. Interesting topic

Great tips about testing, easy to follow. Please bring stickers again :)

Nice ideas, but lecture could be better presented.