The aspnetcorelearning from karm435

Software Testing, very broad term to talk about. What we are going to discuss here

Basics
Automated testing using Unit tests and Integration tests specific to Web app using Aspnetcore3
Adding conventional test using Best.Conventional library
Using Bogus Library to create data for dev environment
How to manage in Memory database/Real database data for integration tests

All of the above using

aspnetcore
sql server
xUnit
Moq

Basics Naming I usually follow the guidelines given on MSDN while writing tests. It has nice examples of explaining the naming conventions.

I like the important note in the docs.

It's important to get this terminology correct. If you call your stubs "mocks", other developers are going to make false assumptions about your intent.

I would encourage give this article a read to get better understanding of Mocks and Stubs.

Dependency Injection

DI is one of the basic building blocks to enable components ready for testing.

Structure of each Test

Arrange
Act
Assert

These names are self explanatory, for each test we Arrange the data that need for the test then we act on the the SUT (System under test) and then we do assertions on the results.

Mocks

What do we need to mock?

Configuration
Database
Logger

Mocking configuration

var mockConfiguration = new Mock<IConfiguration>();
mockConfiguration.Setup(m => m[It.Is<string>(s => s == "ConfigurationKey")]).Returns(<ConfigurationValue>);

Database

We have configured the database as a service and we have the ability to use whatever database we like. I have setup 3 base classes to use 3 different databases. I can choose whichever database I like depending on the test.