by Michael Bodnarchuk

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