Testing101
Onion-architecture-ASP.NET-Core
| Testing101 | Onion-architecture-ASP.NET-Core | |
|---|---|---|
| 5 | 1 | |
| 7 | 763 | |
| - | - | |
| 1.7 | 0.0 | |
| 11 months ago | over 1 year ago | |
| C# | C# | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Testing101
-
Don't duplicate logic in Asserts: The most common mistake on unit testing
Let's write some tests for Stringie, a (fictional) library to manipulate strings with a fluent interface. Stringie has a Remove() method to remove substrings from the end of a string.
-
How to create custom assertions in C# with MSTest
With this new assertion method, we can refactor one of our tests for Stringie, a (fictional) library to manipulate strings. We used Stringie to learn 4 common mistakes when writing tests and 4 test naming conventions.
-
Unit Test Best Practices: On Assertions
For example, let's bring back one test for Stringie, a (fictional) library to manipulate strings, to show the AAA pattern. Notice how each test has these 3 parts. For the sake of the example, we have put comments in each part. You don't need to do that on your own tests.
-
4 naming conventions to better name your tests
If you want to practice naming unit tests, check my Unit Testing 101 repository.
-
4 common mistakes when writing your first unit tests
If you want to practice identifying and fixing these mistakes, check my Unit Testing 101 repository. You will find the tests that Stringie developers wrote and some other misatkes mistakes they made. Your mission, Jim, should you choose to accept it, is to fix them.
Onion-architecture-ASP.NET-Core
What are some alternatives?
Fluent Assertions - A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3.
CleanArchitecture - Clean Architecture Solution Template for ASP.NET Core
ToDoApp-Clean-Architecture - ASP.NET Core Web API and ReactJS to do full stack management application implementing JWT and clean architecture with the repository pattern and CQRS. https://tobedone.works/
sample-dotnet-core-cqrs-api - Sample .NET Core REST API CQRS implementation with raw SQL and DDD using Clean Architecture.
FileApi - An example of REST API for uploading and converting files using minimal API, Clean Architecture and design patterns. ASP.NET Core 8.0
AuthApi - An example of Authentication and Authorization in REST API using minimal API, Clean Architecture and design patterns. ASP.NET Core 8.0
WeatherApi - An example of REST API for handling weather data using minimal API and Clean Architecture with various design patterns. ASP.NET Core 8.0
qest - A simple, cross platform, command line tool to test MSSQL procedures
eisk.webapi - Project based on latest .NET (v6.0) technologies for building scalable web api, along with clean architecture patterns.
IntegrationTestAuth - Mock Authentication And Authorization in ASP.NET Core Integration Tests
UserManagement - ASP.NET Core 3.1 with Angular 10 clean architecture learning path.