Did you ever deploy an application and forgot to add the [Authorize] attribute to a controller or action? I did, and it meant that the application was open to the public and one controller could be used without logging in. Let me show you how you can use reflection and Fluent Assertions to check for the existence of an attribute on a specific class. I’m using this to verify the Authorize attribute on all classed that inherit from ControllerBase in a .NET Core application, but this principle...
