Getting started with unit and functional testing
0 likes122 views
This document discusses the importance of testing code and different types of tests. It covers unit tests, integration tests, and end-to-end tests, explaining what each tests and providing examples. It also discusses best practices for writing good unit and integration tests, including testing behavior not implementation, avoiding dependencies, and using mocking and dependency injection. The goal is to establish a culture of testing code to ensure quality and prevent bugs.
Getting started with unit and functional testing
- 1. Getting started with Testing Adewale Andrade. 28/07/2017, Salvador, Bahia
- 2. WHY TEST? ○ Know that your code works…(and doesn’t breaks anyone else’s). ○ Make deliveries and deploys more stable…. ○ Saves time (and pain) wasted on bug fixing later… ○ Improving code designs and refactoring… ○ Reduce fear of failing...
- 3. TYPES OF TESTS (most common) ○ Unit Tests: ● Tests a small part of the application independently from other parts; (Testing one class’s method); ○ Integration Test (Functional Tests): ● Tests different parts of the application working together; (Testing a controller using multiple classes) ○ End-To-End Tests (E2E): ● Tests whether the flow of an application performs as designed from start to finish; (Testing a login flow)
- 4. OUR STACK ○ PHPUnit ○ Neos Flow ○ PHP 5.5.9 ○ Apache 2
- 5. OK… BUT….. What are we really testing?
- 7. “When testing, face the code like a complete stranger… You have no idea how it does what it should do… But you know your expectations!
- 8. WHAT MAKES A GOOD UNIT TEST? ○ Unit tests should be: ● Easy to write; ● Easy to read; ● Fast; ● Not an integration test ■ No access to external resources (network, databases, file systems, etc.)
- 9. A SIMPLE UNIT TEST
- 10. A SIMPLE INTEGRATION TEST
- 11. WHAT DO YOU NEED TO KNOW? ○ What are you testing? ○ How should it behave? ○ What are the edge cases? ○ Mapped entries? ○ Expected results?
- 12. OK… BUT….. Does the code quality even matter?
- 14. THINGS TO AVOID As much as possible!
- 17. WHEN TO USE EACH ONE ○ Unit Tests: ● Models ● Services methods that don’t have internal dependencies; ○ Integration Tests: ● Controllers; ● Services; ● Repositories;
- 18. HANDLING DEPENDENCIES ○ Unit tests: ● Maybe you should refactor it…. ● Dependency Injection; ● Mocking; ● Maybe it is an integration test; https://jtreminio.com/2013/03/unit-testing-tutorial-part-4-mock-objects-stub-methods-depen dency-injection/
- 19. HANDLING DEPENDENCIES ○ Integration tests: ● Dependency Injection; ● Mocking; ● Do not mock things that you are testing.
- 20. Show me the code! Finally… some action!
- 21. REINFORCING THE CULTURE ○ Pull Requests + Code Review ○ Continuous Integration Servers ● Coverage Tests ● Build Breaking and Notifying ○ Leading by example
- 22. Thanks ;) “With faith, my brother” Adewale Andrade Software Engineer @Agilize Contabilidade Online [email protected]