CleanArchitecture
xUnit
CleanArchitecture | xUnit | |
---|---|---|
18 | 37 | |
15,030 | 4,068 | |
- | 1.9% | |
8.7 | 9.2 | |
7 days ago | 3 days ago | |
C# | C# | |
MIT License | GNU General Public License v3.0 or later |
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.
CleanArchitecture
-
Dotnet.World.News(Wednesday, September, 20, 2023)
🔴 [CleanArchitecture] (Learning Template + Docs): A starting point for Clean Architecture with ASP.NET Core. Clean Architecture is just the latest in a series of names for the same loosely-coupled, dependency-inverted architecture.
- Advice for the web API app development using clean architecture in .NET 6.
- Не знаю где задать этот вопрос
- Where can I learn more about Design Patterns & Clean Architecture in .NET?
-
Learning .NET core as a front-end developer
Here’s a few: - complex domain driven example using vertical slice - another DDD example - clean architecture template by Jason taylor - clean architecture template by ardalis
-
Ask HN: Examples of Top C# Code?
This repository is a good place to start with modern c# code, specifically ASP.NET
https://github.com/ardalis/CleanArchitecture
-
API’s in ASP.NET
If you want to try clean architecture, you can check out Steve smith’s repo or Jason Taylor’s repo.
- Tips to develop a Blazor Server app that’s easy to migrate to WASM in the future
-
Measuring maintainability metrics with NDepend
🔗 Clean Architecture repository | GitHub
-
Confused on how to structure my API with Entity Framework
Overall i now use a DDD style approach with Mediatr based on https://github.com/ardalis/CleanArchitecture/tree/main/src as well as snippets from Microsofts https://github.com/dotnet-architecture/eShopOnWeb
xUnit
-
Optimizing C# code analysis for quicker .NET compilation
Several well-known NuGet packages such as xUnit.net, FluentAssertions, StyleCop, Entity Framework Core, and others include by default a significant number of Roslyn analyzers. They help you adhere to the conventions and best practices of these libraries.
-
Integration testing in Umbraco 10+: Validating document types
Most of my rules apply to document types, so let's build some tests for document types. We start by creating a new test class and a new test function and getting a list of all document types. This test is created using xUnit and FluentAssertions:
-
Comprehensive Unit Testing: A Line-by-Line Approach
xUnit -> https://xunit.net/
-
CI/CD Pipeline Using GitHub Actions: Automate Software Delivery
.NET / xUnit / NUnit / MSTest
-
Fluent Assertions: Fluently Assert the Result of .NET Tests
This library extends the traditional assertions provided by frameworks like MSTest, NUnit, or XUnit by offering a more extensive set of extension methods. Fluent Assertions supports a wide range of types like collections, strings, and objects and even allows for more advanced assertions like throwing exceptions.
-
FluentValidation in .NET
You can verify the functionality of this validator by writing the following tests (using xUnit):
-
Running a XUnit test with C#?
The git repo has other runners. AssemblyRunner appears to be the best fit for an already compiled tests project, but there is a runner that can be wrapped into an MSBuild task for example.
-
Setting up a simple testing project with C#
At this point you're going to see a familiar screen asking you to select a project. Here we're looking for a test project. By default, Visual Studio gives you access to 3 different testing frameworks based on your choice of project. These are MSTest, XUnit and NUnit. Ultimately, all 3 of these testing accomplish the same thing, and I've worked with all of them at various points in my career. The difference is mainly in exact syntax and documentation. Although, it's generally considered that MSTest is a little "older" than NUnit or XUnit, so I tend to see it less now. For the purposes of this demo, I'm going to go with NUnit:
-
Integration tests for AWS serverless solution
xUnit unit tests tool
-
Test-Driven Development
Use a testing framework: Utilize a testing framework like NUnit, xUnit, or MSTest to create, organize, and run your tests. These frameworks provide a consistent way to write tests, generate test reports, and integrate with continuous integration tools.
What are some alternatives?
CleanArchitecture - Clean Architecture Solution Template for ASP.NET Core
Shouldly - Should testing for .NET—the way assertions should be!
AutoMapper - A convention-based object-object mapper in .NET.
NUnit - NUnit Framework
blazor-starter-kit - Clean Architecture Template for Blazor WebAssembly Built with MudBlazor Components.
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.
MassTransit - Distributed Application Framework for .NET
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
JHipster.NET - JHipster.NET blueprint
NSubstitute - A friendly substitute for .NET mocking libraries.
Havit.Blazor - Free Bootstrap 5 components for ASP.NET Blazor + optional enterprise-level stack for Blazor development (gRPC code-first, layered architecture, localization, auth, ...)
MSTest - MSTest framework and adapter