dotnet-testcontainers
FluentDocker
Our great sponsors
dotnet-testcontainers | FluentDocker | |
---|---|---|
6 | 3 | |
1,129 | 1,291 | |
- | - | |
7.3 | 1.8 | |
almost 2 years ago | 7 months ago | |
C# | C# | |
MIT License | 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.
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.
FluentDocker
-
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 have a blog post on setting up docker in your integration tests. Want to refactor it to use fluent docker eventually but works well for now.
-
Help understanding how to write tests for code that performs actions on databases & Local files
I would just stick to integration tests here. The good news is you're using docker already, why not spin up a docker container of the database in your tests? Fluent Docker is a great tool for this.
What are some alternatives?
NUnit - NUnit Framework
Wkhtmltopdf.NetCore-deprecated - Rotativa + Net Core
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.
easyWSL - Create WSL distros based on Docker Images.
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
one-script-wsl2-systemd - The one-script variant of the systemd hack for WSL2
harbor - Dotnet CLI tool to help easily handling development dependencies
Ombi - Want a Movie or TV Show on Plex/Emby/Jellyfin? Use Ombi!
LocalDb - Provides a wrapper around SqlLocalDB to simplify running tests or samples that require a SQL Server Database
WSLHostPatcher - Dynamic patch WSL2 to listen port on any interface.
marionette - Marionette is a test automation framework based on image and text recognition for .NET.
ModernFlyouts - A modern Fluent Design replacement for the old Metro themed flyouts present in Windows. [Moved to: https://github.com/ModernFlyouts-Community/ModernFlyouts]