Just wanted to reach out and say this article was exactly what I was looking for as someone who is new to angular but experienced in software development.
There is so much content out there geared toward beginners since they are the largest audience but that content has too much background info to slog through if you are already familiar with general software engineers concepts. I don't need to learn the difference between a fake and a mock, I don't need any background info on how the browser APIs work, I just want to learn about the details of the angular router abstractions.
It is refreshing to read an article that will just lay out the dependency graph and say "This is the boundary they are faking. These are the additional methods on the fake. No you don't need to reference the fake in your tests unless you are literally testing the router, just use the public interface." etc.
👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
Thank you for your feedback, @kevinaud
. I'm glad the article was well-suited for you. It took me 3 years of professional and spare-time Angular development to figure this out 😄
Just wanted to reach out and say this article was exactly what I was looking for as someone who is new to angular but experienced in software development.
There is so much content out there geared toward beginners since they are the largest audience but that content has too much background info to slog through if you are already familiar with general software engineers concepts. I don't need to learn the difference between a fake and a mock, I don't need any background info on how the browser APIs work, I just want to learn about the details of the angular router abstractions.
It is refreshing to read an article that will just lay out the dependency graph and say "This is the boundary they are faking. These are the additional methods on the fake. No you don't need to reference the fake in your tests unless you are literally testing the router, just use the public interface." etc.
Thanks again!
Thank you for your feedback, @kevinaud . I'm glad the article was well-suited for you. It took me 3 years of professional and spare-time Angular development to figure this out 😄
An evolution of this article series is the Spectacular feature testing API. Let me know what you think.