Coding Short: Is This Thing On? Testing APIs in .NET Core

[@AceSyntaxx]

Thanks Shawn for a succinct explanation of the basics.

[@rustamhajiyev]

Thanks for caring about us 😅 Great one as usual 👍😃 In our projects we usually use integration tests, in a similar way that you demonstrated. We also use LightBDD + pattern given/when/then and write tests in a story like way, so anyone can read and understand them.

[@jamesgranberry8801]

Shawn Wildermuth “cares about me?!” Awww. Lol!

[@MyCodingDiary]

Wow, this video is amazing!😲 Your programming skills are truly impressive.

[@godfathermikal]

I like that you used web app factory. This seems to be a fantastic tool to have in the bag. Would love to see more on how you use it for more than quick demo tests.

[@alessandropinto1529]

Thank you Shawn, I was wondering how to set up Integration tests inside the solution (I generally use an external tool), and it was really illuminating for me

[@catfishfortesque-smythe437]

I don't think that IClassFixture works in this way: from the xUnit Documentation, this creates a single object which is then shared with all test in a class - and it's the test class that has a new instance for each test, with the shared fixture being passed to it. I.E it is only created once, and so does not provide a clean object. To achieve that, you would need to use constructor / dispose in the test class to have a new object instance created. IClassFixture is intended to avoid expensive initialisations.

[@JesseLiberty]

At 1:20 or so you refer to your new favorite toy for developing APIs. Can you say more about it (what the name is, what it does, why it is better than Postman)? Thanks! - jesse

[@prasadgopi831]

Informative and straight to the point. Will there be any session recordings of kcdc event 2023 available anywhere?

[@swildermuth]

Unfortunately, it wasn't recorded.

[@sanglin9387]

my opinion no unit test junk , integeration test

[@swildermuth]

I don't actually agree, I think there is value in unit tests, but trying to unit test for code coverage is a waste of time. IMHO

[@sanglin9387]

@@swildermuth people will do by pass code just to make 100% not to test foreign key , output and input . Unit test maybe good before real implementation but once back end and front end good to go , integration test is the way to go . Most sample unit test a + b , most in real life got formula so on , so we need to make sure it work first in first out .