Aleksei Zagoskin
Software Architect, Staff Engineer
When you check an exception message do you think it might be worth using a constant template for the error message to don't break a test just because you have changed the message, or better to have the test broken on each change of the message and amend it accordingly?
Test Strategy for Example 2 maybe should contain checking that we don't change any other user's entity field but only password. But this could mess up the test. What do you think? What is your assessing path to decide whether include or not anything to test?
I know it is out of the scope of the topic but I'd like to know your opinion, what is the strategy of using cancellation tokens in your examples. I guess the UserManager is invoked by an action (as part of a controller) and then from UserManager you call a repo and pass ct to it. Inside repo you pass ct to linq async operation. What is the benefit to do that? What is the source of the ct? Who and why might cancel the token in the presented chain of calls?
Hi Alexey, thank you a lot for the knowledge sharing and insides, it is very interesting, keep going!
Roman Izosimov
What tool you are using to check test coverage? You've shared a screenshot with us but not its name :)