dockertest
vcr
dockertest | vcr | |
---|---|---|
48 | 20 | |
3,970 | 5,750 | |
1.0% | 0.2% | |
3.0 | 6.4 | |
2 days ago | about 1 month ago | |
Go | Ruby | |
Apache License 2.0 | Hippocratic License 2.1 |
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.
dockertest
-
Testcontainers
I am using https://github.com/ory/dockertest for tests, specifically for databases. Is there any advantage to use Testcontainers?
-
Level UP your RDBMS Productivity in GO
Now, let's run the tests. For this purpose, we are going to use dockertest, but test containers is also a good solution.
-
Golang testing using docker services via dockertest
During my path learning go so far I have come across some amazing libraries and utilites, one of my favourite for integration testing is dockertest.
-
How to start a Go project in 2023
Things I can't live without in a new Go project in no particular order:
- https://github.com/golangci/golangci-lint - meta-linter
- https://goreleaser.com - automate release workflows
- https://magefile.org - build tool that can version your tools
- https://github.com/ory/dockertest/v3 - run containers for e2e testing
- https://github.com/ecordell/optgen - generate functional options
- https://golang.org/x/tools/cmd/stringer - generate String()
- https://mvdan.cc/gofumpt - stricter gofmt
- https://github.com/stretchr/testify - test assertion library
- https://github.com/rs/zerolog - logging
- https://github.com/spf13/cobra - CLI framework
FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb
We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers
-
Beginner-friendly API made with Go following hexagonal architecture.
I've used dockertest a bunch and it is really amazing.
-
How to unit test your database interactions with Docker
Reminds me of https://github.com/ory/dockertest
-
When to mock and what to mock in a Web API?
If your project is relatively simple and you can get away with recreating your scenarios against a real mock database and run other related services locally. It would be good to setup docker containers for your test scripts and write e2e tests. I believe e2e tests are harder but more useful in understanding/reasoning how users are impacted.
-
Don't Mock the Database
Just a heads up, the repository in your comment is invalid, the correct link is https://github.com/ory/dockertest
-
Mocking database calls without a library?
Don't mock. Use https://github.com/ory/dockertest to actually run tests against a dockerized DB.
-
Different SQL drivers for test and production
Use a library like ory/dockertest to spin up a test database for integration tests. It's easy to use, and tests are still fast. It'll take a minute to download the mysql docker image the first time. But, once it's been downloaded, starting the db, running migrations, and running the tests is still pretty quick.
vcr
-
Creating integration tests for a backend legacy codebase
Basically, it's a record/replay tool, similar to VCR for Ruby, but on steroids and powered by AI (khm GPT khm).
-
I isolated the entire codebase from external data sources and made a generator of automated tests
I don't think it's right to say "pythagora generates integration tests". It's more of a "replay manual tests as fixtured unit tests," which makes it similar to (but more powerful than) VCR for Ruby HTTP. What I've always wanted for these kinds of "request recorders" is a way to re-validate the test fixtures over time.
-
Write SDK “base” in Rust, wrap in other languages?
For example, they might expect to be able to mock calls to your API with something like VCR or Responses.
-
How to unit test your database interactions with Docker
I also started from the same starting point but then discovered and started using VCR for creating http stubs - https://github.com/vcr/vcr. It allowed me to write against more realistic and complex test scenarios but didn't support databases.
-
When to mock and what to mock in a Web API?
If you had bit more complex workflows or less time - you could start using a VCR library to mock out API interactions and then continue with your dockerised DBs.
-
Ask HN: When an API is down, what do you usually do?
I generally will use vcr[0] or something similar to record requests and then I write tests and code against that.
3rd parties go down, it happens. In general a system that is dependent on a third party should have some non exceptional behavior when that happens.
So if I’m not setup with vcr, and 3rd party is down- I would on the behavior for what happens when it’s down.
[0] https://github.com/vcr/vcr
-
Are there any testing frameworks to intercept HTTP and Database calls?
With external APIs, you can also make use of a gem like VCR. I prefer mocks (plus unit tests around the actual deserialization of the response) to VCR in most cases, but the end result is about the same.
-
Configure VCR with RSpec
A way to avoid this is using the VCR gem.
-
Testing Dependencies: Fake It While You Make It
We'll use a tool called vcr to capture real HTTP requests and responses, storing and using them from then on. VCR's language and terminology leans heavily into its real-world analogue. If you don't know what a VCR is, it's a box we used to hook up to TVs to watch movies before DVD players. If you don't know what a DVD player is, it's a box we used to hook up to TVs to watch movies before streaming.
-
New grad job as Quality Engineer and seeing only negativity about it
[1] https://github.com/vcr/vcr
What are some alternatives?
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.
Parallel Tests - Ruby: 2 CPUs = 2x Testing Speed for RSpec, Test::Unit and Cucumber
fake-gcs-server - Google Cloud Storage emulator & testing library.
Knapsack - Knapsack splits tests evenly across parallel CI nodes to run fast CI build and save you time.
mockaroo - Mock-A-🦘 (mock-aa-roo) a comprehensive HTTP/HTTPS interface mocking tool for all your development and testing needs!
Spring - Rails application preloader
venom - 🐍 Manage and run your integration tests with efficiency - Venom run executors (script, HTTP Request, web, imap, etc... ) and assertions
timecop - A gem providing "time travel", "time freezing", and "time acceleration" capabilities, making it simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
Ruby-JMeter - A Ruby based DSL for building JMeter test plans
go-sqlmock - Sql mock driver for golang to test database interactions
httparty - :tada: Makes http fun again!