capybara_discoball
vcr
capybara_discoball | vcr | |
---|---|---|
1 | 20 | |
128 | 5,750 | |
0.0% | 0.1% | |
0.0 | 6.4 | |
over 2 years ago | about 1 month ago | |
Ruby | Ruby | |
MIT License | 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.
capybara_discoball
-
Testing Dependencies: Fake It While You Make It
We can use the FakeWeather API rather than the real one using a tool like capybara_discoball.
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?
Appraisal - A Ruby library for testing your library against different versions of dependencies.
Parallel Tests - Ruby: 2 CPUs = 2x Testing Speed for RSpec, Test::Unit and Cucumber
Knapsack - Knapsack splits tests evenly across parallel CI nodes to run fast CI build and save you time.
Spring - Rails application preloader
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.
Ruby-JMeter - A Ruby based DSL for building JMeter test plans
httparty - :tada: Makes http fun again!
mutant - Automated code reviews via mutation testing - semantic code coverage.
WebMock - Library for stubbing and setting expectations on HTTP requests in Ruby.
Zapata - An Automatic Automated Test Writer
puffing-billy - A rewriting web proxy for testing interactions between your browser and external sites. Works with ruby + rspec.