I have a few different videos about testing on my channel, some of them are a bit older now. The only "proper" guide to testing I have is this module on Elite Ionic: eliteionic.com/modules/test-driven-development/ some of the lessons are free but it is part of a paid course

Which one were you interested in? There's a bunch of different repos I'm showing in this video

@@JoshuaMorony That one with `Complex Stream`

@@Charon061 sure: github.com/joshuamorony/ionicstart-snapaday/blob/insta-story-v2/src/app/slideshow/slideshow.component.ts

@@JoshuaMorony Would you mind linking the repo for the LoginStore spec example?

For me it's just always Component Store until Store becomes apparently necessary, but for me I never run into those situations - I think the benefit usually comes up more in larger teams with more complex apps, and I am generally just developing alone. However, if you are productive with Store and like using it, then I think there is no reason not to use it even for the most simple circumstances (although it still probably makes sense to use Component Store for state that is local to just a single component - but again, that's up to you).

I've been doing E2E tests with Cypress in Angular for a long time, but I haven't touched component testing with Cypress yet

@@JoshuaMorony have you made videos on Cypress?

@@MattBodman I have a few where I use Cypress like this one: kzfaq.info/get/bejne/q8uWetCDyK_RY5c.html generally any of my videos on TDD or E2E - but I don't really have a deep dive into how Cypress works or anything like that

I make a point to never change my code to make the tests viable, and often you do run into situations like this where you can't access something because it is private - but then I always just change the test because with the black box style approach I shouldn't need to access private things. In this case, the subjects are actually meant to be public as I am next-ing them from the template. However, if they were private and say I had methods being called from the template instead then I would either just trigger that method instead of nexting the subject, or I could also trigger the click handler in the template if I wanted to as well.

@@JoshuaMorony Solid answer. I think with the recent update of making protected members accessible by the template, it seems like even in this case, those subjects could be protected and hard to get to, which I guess would just leave triggering the clicks as your input to the test?

@@michaelfaith yes I think that would be the most correct way to do it (triggering a click) as that is how it would actually be interacted with, my approach at the moment makes the tests a bit easier/nicer to write but also run the risk of being bitten by a refactor (i.e. if a code reviewer like yourself wanted to make those class members protected before merging lol)

The apps in this video aren't using Nx, but yes Jest was installed separately using the briebug schematic