I've been using test harnesses since they were inbtroduced and for unit tests, these have been a great boon. There are two points that continue to bother me daily: 1. The async test harness API won't win a prize for ergonomics, I routinly extract calls nested five layers deep into functions in order to do something banal, like triggering a mat-tooltip and getting its value. 2. Anemic story for harnesses outside of unit test. My E2E tests leverage TestCafe and instead of re-using existing harnesses, I have to write my own harnesses in compatible format. These are always much simpler to use, though thanks to the fuild chainable `TestController` API.
Shout-outs to the Angular material-team for making our life easier! Loved this talk Alisa! 😎
Agreed! Shout out to Angular Material team! Thanks for your kind words, Markus! ❤
I've been using test harnesses since they were inbtroduced and for unit tests, these have been a great boon. There are two points that continue to bother me daily:
1. The async test harness API won't win a prize for ergonomics, I routinly extract calls nested five layers deep into functions in order to do something banal, like triggering a mat-tooltip and getting its value.
2. Anemic story for harnesses outside of unit test. My E2E tests leverage TestCafe and instead of re-using existing harnesses, I have to write my own harnesses in compatible format. These are always much simpler to use, though thanks to the fuild chainable `TestController` API.