logcorner / asp.net-web-api-core-integration-testing-using-inmemory-entityframeworkcore-sqlite-and-xunit2 Goto Github PK

Compared to unit testing, Integration testing gives us a better return on test investment. Nowadays, we have a lot of tools to set it up easily, and it can go faster and give us more confidence with code we have changing knowing we have not breaking existing functionalities. It can help us to catch regression errors, before we deploy to a test environment, and fewer bugs in new features, resulting Higher velocity and higher quality solution Unit testing test behaviour of a class and drive its implementation, run in memory and mocks the Data Acces Laywer while Integration testing test the entire system and focus on interactions between many classes, uses the real database and test the Data Acces Laywer and its value is to catch regressions. So Integration testing may catch errors that passes on unit testing In this tutorial, I will talk about Asp.Net Web Api Core Integration testing using InMemory EntityFrameworkCore Sqlite and Xunit2

Home Page: http://logcorner.com/