- About the author
- Questions and Issues
- Edit and Contribute
- Introduction
- 1. Workshop Overview
- 2. KnockoutJS
- 3. Background
- 4. Features/Blades
- 5. Apps & Aspects
-
6. Services & the ServiceRegistry
- 6.1. Services
- 6.2. ServiceRegistry
- 6.3. Problems Solved
- 6.4. Developer Environment Dependencies
- 6.5. Required Dependencies
- 6.6. No Backend Dependencies
- 6.7. Configuring Services
- 6.8. Workbenches
- 6.9. Modular App Services
- 6.10. Modular App Services
- 6.11. User Service
- 6.12. Chat Service
- 6.13. Exercises Overview
- 6.14. Exercise: Input Blade & Services
- 6.15. Exercise: Messages Blade & Services
- 6.16. Exercise: User Card Blade & Services
- 6.17. Retrospective
- 7. Apps & Aspects (again)
- 8. Extras
- 9. That's a Wrap!
- 10. Reference
Full Feature Testing
From the earlier exercises you'll remember that we used an MVVM solution for our UI. In combination with services this means we can actually test our full feature in isolation.
We can:
- Interact with the View Model and make assertions against the interactions that took place with Services
- Inject a test double/fake service into the ServiceRegistry, get it to behave in a certain way to test a feature requirement, and then assert the state of the View Model
