DEV Community

Introduction to ASP.NET Core Integration Testing

Kai Oswald on September 10, 2019

In this post I'll give you a quick introduction into how you can test your ASP.NET Core Controllers. Please note that the term "Integration Testin...

Read full post

Tomas Mūžas • Sep 11 '19 • Edited

Hey, nice post! Just my two cents, but I believe you can use Assert.Equal on collections as well, cleaning up quite a lot of code :)

Kai Oswald • Sep 13 '19

It doesn't, but there's a neat utility class for Collections called CollectionAssert which I just found that does that!

So the code could be cut to:

CollectionAssert.AreEqual(expectedResponse, actualResponse);

Filippenko Kirill • Sep 13 '19

Good post. But how would you test authorized endpoints?

Kai Oswald • Sep 13 '19

This depends on the authorization methods used to protect those endpoints.

For example if you use JWT you could generate your token in the TestInitialize and set the Authorization header on the client.

I'm planning on doing another post going into more detail.

Filippenko Kirill • Sep 13 '19 • Edited

Good point.
But if you're ought to create and API for SPA, you'd probably consider not only 'header' implementation.
For those reasons I personally prefer to send JWT in HttpOnly cookie. Could you please cover this case as well?

Kai Oswald • Oct 7 '19

Just published the second post covering Cookie and JWT authentication!

ASP.NET Core Integration Testing: Protected endpoints

Kai Oswald ・ Oct 7 ・ 4 min read

#testing #aspnetcore #csharp #dotnet