integresql
testcontainers-node
| integresql | testcontainers-node | |
|---|---|---|
| 5 | 26 | |
| 710 | 1,682 | |
| 4.9% | 11.2% | |
| 8.9 | 8.4 | |
| 3 months ago | 3 days ago | |
| Go | TypeScript | |
| 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-node
-
Multiple MongoDB Databases on Spring Boot
To be able to test for multiple databases, I recommend you using Testcontainers. That's my configuration to start the container:
-
Show HN: I open-sourced the in-memory PostgreSQL I built at work for E2E tests
I don't get it either. Why not use something like https://testcontainers.com/?
- Utilizando Testcontainers para Testes de Integração com NestJS e Prisma ORM
- Testcontainers
-
Rust Tooling: 8 tools that will increase your productivity
Testing with added infrastructure can be quite tricky. testcontainers aims to solve this by providing an open-source framework for providing local, lightweight containers for your application that can be immediately thrown away after use. It also has a Rust SDK!
-
Run and test DynamoDB applications locally using Docker and Testcontainers
This is a good start. But DynamoDB Local is a great fit for Testcontainers which "is an open source framework for providing throwaway, lightweight instances of databases, message brokers, web browsers, or just about anything that can run in a Docker container."
- API completa em Golang - Parte 7
- We built our customer data warehouse all on Postgres
-
Quarkus : Greener, Better, Faster, Stronger
Devservices supports the automatic provisioning of unconfigured third party services in development and test mode. They can be provided by extension leveraging (usually) TestContainer library.
-
The day I started believing in Unit Tests (2023)
I hadn’t heard of Test Containers[1], but it looks really useful - thanks for the rec.
[1] https://testcontainers.com/
What are some alternatives?
flyway-spawn-demo - CI demo using Flyway and Spawn
nestjs-testing - Testing tutorial using NestJs
otj-pg-embedded - Java embedded PostgreSQL component for testing
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
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.
jest - Delightful JavaScript Testing.
spawn-demo - Demo application to show how Spawn can be integrated in Development and CI
mocha - ☕️ simple, flexible, fun javascript test framework for node.js & the browser
entr - Run arbitrary commands when files change
Cucumber.js - Cucumber for JavaScript
localstripe - A fake but stateful Stripe server that you can run locally, for testing purposes.
TestCafe - A Node.js tool to automate end-to-end web testing.