From time to time it might happen, that you need to test certain parts of your ASP.NET Core<\/i> configuration without hitting publicly visible business-related controllers. For instance, in my case, I wanted to make sure that my ASP.NET Core API<\/i> behavior is consistent with the original API<\/i> written in Nancy<\/i>. As you might expect there are quite a lot of differences between both of the frameworks, so let’s focus on testing one thing, namely non-nullable reference type handling. Long story short, in order to have the same behavior in ASP.NET Core<\/i> as in Nancy<\/i> I had to add the following line of configuration<\/p>\n This one prevents ASP.NET Core<\/i> from marking non-nullable reference type properties in request as required. Having that configuration ready, I wanted to test it with an end to end test. Because there was no business-related logic yet, I needed to figure out the way of adding API<\/i> controllers to my application directly from the integration tests. Here is how you can achieve that.<\/p>\n ASP.NET Core<\/i> is able to compose your API<\/i> from different parts thanks to ApplicationPartManager<\/i>. By default, you don’t use it directly but rather with IMvcBuilder AddApplicationPart<\/i> extension method while setting up your application<\/p>\n\r\n\/\/ This method gets called by the runtime. Use this method to add services to the container.\r\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddControllers(opts => opts.SuppressImplicitRequiredAttributeForNonNullableReferenceTypes = true)\r\n .AddNewtonsoftJson();\r\n}\r\n<\/pre>\n2. Accessing ApplicationPartManager from integration tests<\/h3>\n
\r\n\/\/ This method gets called by the runtime. Use this method to add services to the container.\r\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddControllers()\r\n .AddApplicationPart(typeof(SomeClass).Assembly)\r\n .AddNewtonsoftJson();\r\n}\r\n<\/pre>\n