The document discusses the importance of testing in Symfony2, focusing on various tools and methodologies such as BDD, TDD, and unit testing. It emphasizes the need to understand business values, avoid improper tool usage, and maintain a structured approach to testing layered architectures. The speaker encourages continuous learning and highlights the distinction between unit and integration tests, providing examples and best practices for effective testing.

1. Testing and Symfony2
Tomasz Łopusiewicz

2. Tomasz Łopusiewicz
tabbi_89
tabbi89
tom@tabbi89.com
About me

3. Agenda
This talk will be about
The tools ExampleWhy Layers
Dlaczego chce powiedzieć o testach i 2 lata
Doodad logo tsh
Na samym koncu w example opisac legacy code z refaktorem

4. Should I test my application
Maybe
Will tests be
readable and
maintainable
Will
design
be betterWill code
be without
any bugs
Are there any
tools that will
help me
Will this
speed up my
development

5. New tools new techniques
The tools
BDD
TDD
Behat
phpspec
Codeception
layered architecture
domain model
…
Narzędzia pokażą nam drogę BDD tests
phpspec tests
Pojawiaja się znaki równa się
BEHAT=BDD

6. Google “symfony2 testing”
The tools

7. My code
The tools
Legacy code :)

8. And my first test …
The tools
PHPUnit + BrowserKit + DomCrawler

9. Google “behat+symfony2"
The tools
Behat + MinkExtension

10. Google “codeception+symfony2"
The tools
Codeception + Symfony2 module

11. phpspec
The tools
“specing” getters and setters
“specing" getters and setters

12. What is wrong
The tools
• We don’t know which tool we should use
• We use tools improperly
• We are too much focused on tools instead of business
values
• We are impatient (it takes time to write good test suites)
• Never stop learning :)

13. Lets start from the very beginning

14. Framework should help You
The tools
It is a controller for Your app
Don’t spread your logic
through controller

15. Each tool can be helpful in different level of You app
Tools summary
< Object level
Describing behaviour
< System level
Describing behaviour
System level
Object level
It is more about testing
System level
Object level
Describing with testing

16. Layered architecture
Layers
Rozprzężenie aplikacji zawsze jest ważne
dla utrzymywania kodu, stąd dla
nietrywialnych aplikacji jest to zasadne.

17. Layered tests
Layers
Production-like environment to verify the system as a whole.
This may include user interfaces, databases, web servers, logging etc.
Verifying that different units are working together.
It focuses on the interfaces between components.
Often integration tests ale slower than unit tests.
A unit test verifies a single behaviour of a single unit
A logical unit is something that can be reasoned about in isolation.
The test should omit the number of other units it touches on.
Should not touch any part outside of your own system.

18. Bad way
Example

19. Good way
Example
If you want to understand business and match their
expectations
• Start with conversation
• Prepare questions about system
• Use examples to correctly understand features
• After all write down all the scenarios You touched
during conversation

20. Our acceptance criteria in scenarios
Example
Logowanie, transakc

21. Start with planning process
Example
Testing service layer

22. Spec behaviour
Example

23. Result
Example

24. The end
Example

25. Use listeners for additional processes
Example

26. Integration test
Example

27. Requirements - transactions, loggers
Example

28. Yes, I should test my application not framework

29. Questions ?
Thanks for coming