dotnet-testcontainers
docker-net-example
Our great sponsors
| dotnet-testcontainers | docker-net-example | |
|---|---|---|
| 6 | 1 | |
| 1,129 | 1 | |
| - | - | |
| 7.3 | 5.6 | |
| almost 2 years ago | 4 months 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.
dotnet-testcontainers
-
How do you Unit Test a WebAPI? What do you test?
So what I usually do is: • Unit test underlying (public) services and application ‘core’ • Integration test (or w/e you call it) an entire functionality flow, by sending in ‘real’ requests on one end, and locally mocking/stubbing the application ‘edges’ that supply the response data. WireMock for requests to external services, H2 or Testcontainers for database.
-
EF Core In-Memory DB (for testing) does not allow List<int> property even though this is something Postgres does. How would I go about testing this?
I'd use testcontainers to spin up an instance of Progress and run against the actual thing. That way you get the benefit of testing against the actual database, but also that you don't have to set up a bunch of stuff locally.
Not every db support array as primitive, if you want to write integration tests and you have access to docker I suggest you testcontainers.
-
Does anyone have a good functional (integration? end to end?) automated Web API testing setup?
There is a rope which can help with this task: https://github.com/HofmeisterAn/dotnet-testcontainers
-
Integration testing with EF Core, part 2
Dotnet.Testcontainers also comes with some built-in classes that wraps various services, one of these classes actually wraps a SQL Server Docker container and there are few more that covers the most common databases e.g.
-
End to end testing is confusing
You should also check out Docker, especially TestContainers. That way you can spin up databases (and other dependencies) on the fly and do operations on them. This means that you don't need to "fake" a database, as you will have access to a new one.
docker-net-example
-
.NET 7 + Docker
You can try cloning from the net6.0 branch from this repository.
What are some alternatives?
FluentDocker - Use docker, docker-compose local and remote in tests and your .NET core/full framework apps via a FluentAPI
ASP.NET MVC Boilerplate - .NET project templates with batteries included, providing the minimum amount of code required to get you going faster.
NUnit - NUnit Framework
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
WireMock.Net - WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality.
testcontainers-dotnet - A library to support tests with throwaway instances of Docker containers for all compatible .NET Standard versions.
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
harbor - Dotnet CLI tool to help easily handling development dependencies
LocalDb - Provides a wrapper around SqlLocalDB to simplify running tests or samples that require a SQL Server Database
marionette - Marionette is a test automation framework based on image and text recognition for .NET.
Mixcore CMS - 🚀 Mixcore CMS is an Future-Proof Enterprise Web CMS that supports both headless and decoupled to easily build any kinds of app/web app/all in all/customizable APIs built on top of ASP.NET Core / Dotnet Core. It is a completely open-source ASP.NET Core (Dotnet Core) CMS solution. https://mixcore.org