pg-transactional-tests
integresql
| pg-transactional-tests | integresql | |
|---|---|---|
| 1 | 5 | |
| 8 | 720 | |
| - | 1.4% | |
| 3.4 | 8.9 | |
| about 2 months ago | 4 months ago | |
| TypeScript | Go | |
| - | 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.
pg-transactional-tests
-
Mock unit test an API that uses postgres or integration test API with a "test" database?
How to clean it between test runs? How to have no conflicts between tests that run in parallel? Here is a library to solve this: pg-transactional-tests, I'm going to update in a near day or two so should be working fine, it served me well previously at work projects.
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
What are some alternatives?
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.
flyway-spawn-demo - CI demo using Flyway and Spawn
otj-pg-embedded - Java embedded PostgreSQL component for testing
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
entr - Run arbitrary commands when files change
localstripe - A fake but stateful Stripe server that you can run locally, for testing purposes.
rush - Production-driven prototyping. This starter is setup in a production-friendly way and will setup tests + dev environment exactly like a live project will work. Works the same both on your laptop or Github CI, so you can go from hacking on your laptop to a full gitops environment.
SS-Unit - A 100% T-SQL based unit testing framework for SQL Server
data-diff - Compare tables within or across databases
dbt-unit-testing - This dbt package contains macros to support unit testing that can be (re)used across dbt projects.
spark-style-guide - Spark style guide