integresql
testcontainers-dotnet
Our great sponsors
| integresql | testcontainers-dotnet | |
|---|---|---|
| 5 | 16 | |
| 710 | 3,534 | |
| 4.9% | 3.2% | |
| 8.9 | 9.0 | |
| 3 months ago | 6 days ago | |
| Go | 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.
integresql
-
Mock unit test an API that uses postgres or integration test API with a "test" database?
For the case of PostgreSQL I've found IntegreSQL and its Javascript client really helpful because it can create a copy of the database per test case, which it helps to write integration tests with real DB calls.
-
Mocking database calls without a library?
Mocking has some advantages, but so does using a real database, at work we use https://github.com/allaboutapps/integresql and I quite like the approach that integresql has, since it makes possible to have a fresh database with your dummy data for every test without impacting the execution speed (compared to dropping an re-creating the database).
-
Ask HN: How do you test SQL?
Happy to hear that! When it comes to testing services that depend on PostgreSQL, this is still my preferred solution.
https://github.com/allaboutapps/integresql
disclaimer: author
- IntegreSQL – isolated PostgreSQL databases for integration tests
-
Pg_tmp – Run tests on an isolated, temporary PostgreSQL database
I haven't had a change to try it yet, but IntegreSQL[0] looks like this on steroids. It allows you to create a template (runs migrations and seed dates), and then uses Postgres's built in cloning functionality to maintain a pool of fresh databases. They claim 500ms to clone a database without the pool, and that the pool pretty much hides the latency entirely.
[0]: https://github.com/allaboutapps/integresql
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?
flyway-spawn-demo - CI demo using Flyway and Spawn
NUnit - NUnit Framework
otj-pg-embedded - Java embedded PostgreSQL component for testing
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
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.
spawn-demo - Demo application to show how Spawn can be integrated in Development and CI
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.
entr - Run arbitrary commands when files change
Docker.DotNet - :whale: .NET (C#) Client Library for Docker API
localstripe - A fake but stateful Stripe server that you can run locally, for testing purposes.
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.