xUnit
Serilog
xUnit | Serilog | |
---|---|---|
36 | 55 | |
4,028 | 6,943 | |
0.9% | 0.7% | |
9.2 | 6.9 | |
6 days ago | 5 days ago | |
C# | C# | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
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.
Serilog
-
Logging in .NET 8 with Serilog and Seq
To learn more about Serilog, you can visit the documentation on their GitHub project. To learn more about Seq, you can visit the documentation on their website.
-
Microsoft Entity Framework Core 8 samples
These projects use dependency injection for connections and have no logging although they are ready to log to the console via SeriLog setup in Program.cs.
-
Logging - How to configure Log Content?
See here: https://github.com/serilog/serilog/wiki/Configuration-Basics e.g.
-
Using toast notifications in Windows Forms
Captured in public static void OnActivated() and note Log is SeriLog.
-
How to set up Serilog "Enrichers"?
"Serilog": { "Using": [ "Serilog.Sinks.File" ], "Enrich": [ "WithHttpRequestId", "WithExceptionDetails", "WithClientIp" ], "MinimumLevel": { "Default": "Information" }, "WriteTo": [ { "Name": "File", "Args": { "path": "../../../../../Logs/MyApp/MyApp-.log", "rollingInterval": "Day", "retainedFileCountLimit": "7", "outputTemplate": "[{Timestamp:yyyy-MM-dd HH:mm:ss.fff zzz} {CorrelationId} {Level:u3}] {Username} {Message:lj}{NewLine}{Exception} {Properties:lj}{NewLine}" } } ] } đŸ‘† I got the enricher names from serilog's wiki. The idea was to log the HTTPRequestId, ClientIp, and automagically log the details of every exception thrown (without having to do _logger.LogError(...)). However I don't see those details in the logs. In Program.cs: ``` var logger = new LoggerConfiguration() .ReadFrom.Configuration(builder.Configuration) .Enrich.FromLogContext() .CreateLogger();
- How to log to an Excel file?
-
How can I fix logger maximum destructuring reached error when using Serilog C#?
You could also write a custom destructuring policy, assuming it's a flurl-specific public exception type and you only need certain properties of it. You'd implement IDestructuringPolicy and then add it to the configuration:
- getting started with loggin
-
A command line tool that converts GraphQL schemas to Karate API tests
Serilog for logging
-
question about TargetFrameworks/multitargetting (new style SDK) csprojs... via serilog example
I've cloned https://github.com/serilog/serilog and I'm not sure what's going on with the multitargetting in the tests? Does this (below) mean, if the dev's OS is windows, then target framework 462 or 471? What should I do on my laptop, which only has the net6 and fw48 sdk installed?
What are some alternatives?
Shouldly - Should testing for .NET—the way assertions should be!
NLog - NLog - Advanced and Structured Logging for Various .NET Platforms
NUnit - NUnit Framework
Log4Net - Apache Log4net is a versatile, feature-rich, efficient logging API and backend for .NET
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.
ELMAH - Error Logging Modules & Handlers for ASP.NET
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
Sentry - Sentry SDK for .NET
NSubstitute - A friendly substitute for .NET mocking libraries.
opentelemetry-specification - Specifications for OpenTelemetry
MSTest - MSTest framework and adapter
Semantic Logging Application Block (SLAB) - Supporting semantic/structured logging for .NET