Mapster
testcontainers-dotnet
| Mapster | testcontainers-dotnet | |
|---|---|---|
| 15 | 16 | |
| 4,145 | 3,550 | |
| 0.8% | 1.9% | |
| 5.5 | 8.9 | |
| 5 months ago | 2 days ago | |
| C# | C# | |
| MIT License | 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.
Mapster
-
Dotnet.World.News(Wednesday, September, 20, 2023)
🔴 [Mapster] A fast, fun and stimulating object to object Mapper! Mapster was designed to be efficient on both speed and memory. You could gain a 4x performance improvement whilst using only 1/3 of memory.
- Mapster and IFormFile exception
-
Object Mapping in .NET
Mapster
-
Help with an ASP.NET Core API and Mapster
Have you read this part in their documentation? https://github.com/MapsterMapper/Mapster/wiki/Data-types
-
Is Automapper the most hated library?
Which is the main reason I don't use it anymore. I can still stand behind why it was created and what it was trying to solve. If you still want to use a mapper I would recommend Mapster as it supports source generation so you can see all code and it's references.
-
When using the DTO pattern and rolling your own mappers, is there a shorter way to write the mapping functions?
Gotta add a shoutout to Mapster which does pretty much the same thing also using source generation.
-
AutoMapper's open source code of conduct
I highly recommend Mapster (https://github.com/MapsterMapper/Mapster)
-
What C# tools would you like to use that don't exist today?
We use Mapster coupled with FastExpressionCompiler and have been very happy with it.
-
Looking for alternative solution to Deep Clone for 10,000+ iterrations
Try Mapster
-
Unit Tests Done Right (Part 2)
I hope I managed to convince you and proved the value of unit tests for mappings, so let's move on to the next example. We're going to use AutoMapper, but from a testing standpoint, the choice of mapper makes no difference. For instance, we can replace AutoMapper with Mapster and it won't affect our tests in any way. Moreover, the existing tests will indicate whether our mapping refactoring was successful or not, which is one of the points of having unit tests 🙂
testcontainers-dotnet
-
Integration tests with AWS S3 buckets using Localstack and Testcontainers
Testcontainers
-
Integration Tests with In Memory DB vs Real DB on Docker
Like others said, it's better to test with an actual database. I recommend using Testcontainers (https://dotnet.testcontainers.org), you can even create multiple instances so your tests can run in parallel independently.
- Unit Testing
- Running untrusted (user-provided) Python code on ASP.NET/C# backend
-
Integration tests for AWS serverless solution
To launch a container in code we will use Testcontainers. Testcontainers is a library that is built on top of the .NET Docker remote API and provides a lightweight implementation to support your test environment in all circumstances. This library supports pre-defined packages for containers or you can use your .dockerfile. We will use a pre-defined package for LocalStak. LocalStack is a cloud service emulator that runs in a single container for AWS service. LocalStack supports a growing number of AWS services.
- If i want to do testing CRUD should I use in memory or just do integration test where I use a seperate database?
-
Do you guys mock everything in your Unit Tests?
Bogus - For creating fake data Verify - Snapshot testing for .NET MELT - For testing ILogger usage Stryker - Mutation Testing for .NET TestContainers - run docker programmatically in integration tests
- Testes de integração com containers
- What C# tools would you like to use that don't exist today?
-
Ask HN: How do you test SQL?
.NET Shop using SQL Server here, but I think something similar to what we do can apply to any stack. We use TestContainers [1] to spin up a container with SQL Server engine running on it. Then use FluentMigrator [2] to provision tables and test data to run XUnit integration tests against. This has worked remarkably well.
[1] https://dotnet.testcontainers.org/
What are some alternatives?
AutoMapper - A convention-based object-object mapper in .NET.
NUnit - NUnit Framework
mapperly - A .NET source generator for generating object mappings. No runtime reflection.
SpecFlow - #1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration
Mapping Generator - :arrows_counterclockwise: "AutoMapper" like, Roslyn based, code fix provider that allows to generate mapping code in design time.
testcontainers-go - Testcontainers for Go is a Go package that makes it simple to create and clean up container-based dependencies for automated integration/smoke tests. The clean, easy-to-use API enables developers to programmatically define containers that should be run as part of a test and clean up those resources when the test is done.
AgileMapper - A zero-configuration, highly-configurable, unopinionated object mapper with viewable execution plans. Flattens, unflattens, deep clones, merges, updates and projects queries. .NET 3.5+ and .NET Standard 1.0+.
testcontainers-python - Testcontainers is a Python library that providing a friendly API to run Docker container. It is designed to create runtime environment to use during your automatic tests.
ExpressMapper - Mapping .Net types
Docker.DotNet - :whale: .NET (C#) Client Library for Docker API
mapr - A simple object to object mapper.
ephemeral-mongo - EphemeralMongo is a set of three NuGet packages wrapping the binaries of MongoDB 4, 5 and 6 built for .NET Standard 2.0.