<aside> 💡 What do I test? How do I test? What is too much testing, and what's too little?
</aside>
Okay, so Angular testing. Seriously one of the most frustrating experiences to learn, but once you get it, you will prevent so much more head ache. When you look up Angular component testing, all you see is some random articles that show you "here is how to get an element", and nothing else that is really helpful. You'll find some obscure stuff, but you're not sure if it really applies.
Now you're here. Let me fix that, because honestly Angular testing is one of the best things you can do to guarantee your app works. I'll whip up a git repo so you can look at the code, but follow along and you'll thank me later.
But I'm gonna preface this with 1 thing. This is the golden rule.
<aside> ⚠️ Every single test you write should tell you something, and every single test you write should protect you from wreckless coworkers! Testing is a function-prescriptive, self-documenting, easy process. If it is not all three of these, you are doing it wrong.
</aside>
Now to preface it with the purpose
<aside> ⚠️ Your testing should be the thing that makes your team leaders confident in the likelihood of a stable release.
</aside>
Okay, so this is an important thing, and the answer is shit. It really depends. But you didn't come here for options, you came here for solutions. So I'll tell you what you should test, and you can decide for yourself later if it makes sense.
This is where you make sure your components actually do the shit that you want them to do. Does that form show an error? Does that button disappear when I click? Does that loading indicator show when it's loading?