Test-Driven Sitecore
Download as PPTX, PDF0 likes787 views
This document discusses test-driven development (TDD) and strategies for testing Sitecore applications. It covers: 1. The basics of TDD including writing unit tests first, making them pass, and then refactoring code. This helps ensure code always works and allows for safe refactoring. 2. Isolating dependencies by using interfaces, dependency injection with AutoFac, and fake objects with NSubstitute to isolate code from external systems. 3. Strategies for isolating and testing Sitecore code, including using Glass Mapper to map Sitecore items to lightweight objects and the Sitecore.FakeDB library for faking Sitecore data. 4. Tools for testing Sitecore itself
Test-Driven Sitecore
- 2. @DanSolovay Sitecore Practice Lead at Velir MVP x 3 dansolovay.com velir.com/blog
- 3. What’s the plan? 1. Unit Testing and Test-Driven Development 2. Isolating dependencies 3. Isolating Sitecore 4. Testing Sitecore itself 5. How to get started
- 4. 1. Unit Testing and Test- Driven Development
- 5. What is a Unit Test? • Can be automated • In memory (no DB or File access) • Consistent & Fast • Single Logical Concept
- 6. Unit Testing is a Waste of Time …unless you plan to make changes to your code.
- 7. Unit Tests Let You… • Change code with confidence • Refactor • Keep code simple • Work well with others
- 8. Test-Driven Development • RED: Make a failing test. • GREEN: Make it pass. • REFACTOR: Make it clean.
- 9. This is stupid! "It's going to slow me down, it's a waste of time and effort, it will just break my flow."
- 10. However… Imagine if you walked into a room full of people working this way. A minute ago, all of their code worked. Robert Martin, The Three Rules of TDD bit.ly/tdd3rules
- 11. Calculator Kata A classic exercise to learn TDD bit.ly/tdd-kata
- 13. Recap • Code is always working • RED: Add functionality • GREEN: Add design • Practice, practice, practice
- 15. Isolation How do I keep out the real world? • Talk to interfaces • Wire with AutoFac • Fake with NSubstitute
- 16. AutoFac • Constructor injection • Interfaces Classes • Code to abstractions
- 17. NSubstitute • Create fakes from interfaces • Script output • Verify input
- 19. Recap • MVC + AutoFac: Interfaces Production Objects • NSubstitute: Interfaces Fakes
- 21. Sitecore and Testability Sitecore items are FAT objects • Knowledge of database • Hard to “new up” • God-like Static methods
- 22. Glass Mapper • Injects items into light objects • Plays well with AutoFac & MVC • Code Gen option Documentation: http://glass.lu
- 24. Sitecore.FakeDB • Creates fake Items • Can fake: • Hierarchies • Templates • Security • Still in Development Github: bit.ly/FakeDB
- 26. Recap • Glass for isolating Sitecore • Sitecore.FakeDB for legacy code
- 27. 4. Testing Sitecore Itself
- 28. Codeflood Test Runner • Available at CodeFlood.net • Useful for testing Sitecore behavior
- 30. Recap • Integration tests talk to real things • Use for testing Sitecore tools • Use unit tests to build logic
- 31. 5. How to Get Started
- 32. Some Practical Tips • Start small. One hour a week. • Pair up. • Keep tests clean. • Keep tests passing. • Do a Kata workshop. • Do TDD Ping Pong.
- 34. To Learn More • My talk videos: bit.ly/tdd-videos • String Calculator: bit.ly/tdd-kata • Alistair Deneys’ blog: bit.ly/sitecore-testing
- 35. Photo Credits Clock: © littlenelly, Flickr Traffic Light: © Niels Sienaert, Flickr Lighthouse: © Dennis Jarvis, Flickr Screwdriver: © Gal, Flickr Dan: © Chris Brady, Velir