�ݺ�ߣ

© 2017 Magento, Inc. Page | 1 ‘17
Automated tests in Magento

Software Engineer at Magento
Ievgen Sentiabov

The tests pyramid in Magento

Why we need tests?
• Never be sure that everything work
• Show how bad architecture
• Facilitate refactoring
• Show how system works
• Tests as documentation

© 2017 Magento, Inc. Page | 6
Unit Tests

Example #1

Example #2

Unit test types
https://martinfowler.com/bliki/UnitTest.html

Mocking...

Testing class dependency

Or not???

BUT
2 Units and 0 Integration

Are unit tests useless?
• Describe unit behavior
• Early show code smells
• Code coverage shows corner cases

Integration Tests

Unit vs. Integration

Benefits of Integration Tests
• Verifying interaction between components
• Catch errors between interfaces
• Show "real" components usage
• Check store dependent configurations
• Based on a system specification

Different Approaches

Does TDD work?

Pitfalls
• Interaction with 3rd party systems
• Complicated fixtures
• Fixtures without rollbacks

Solutions
• Mocking
• Atomic fixtures
• Annotations
@magentoAppIsolation
@magentoDbIsolation
@magentoAppArea

WEB API
Functional Tests

Functional Tests

Disadvantages
• Expensive "cost"
• Very slow
• Hard to debug
BUT
• Cover whole system
• Can be used for 3rd party integrations
• Imitate real customer's behavior

Best Practices

Code coverage

Atomic fixtures
Quote
Items
Address
Payment
Items
Address
Payment
Quote

Clean the state

In general...
• Choose testing strategy
• Write rollbacks for fixtures (WEB API Functional)
• Minimum assertions per test
• Avoid loops and conditions in tests
• Test public code
• Cover corner cases

In the end

Summary
• Writing effective tests is hard
• Tests help find possible bugs earlier
• Improve an architecture
• Allow refactor code safely
• Can be used as system documentation

�ݺ�ߣ

Automated tests in Magento

More Related Content

Automated tests in Magento