-
-
Notifications
You must be signed in to change notification settings - Fork 15
Home
Welcome to the TranscribersOfReddit wiki!
A redis bulk-reply handling package for higher throughput. Once we start hitting limits where redis is becoming a bottleneck, this will become more important.
Aiding in debugging something when an exception is thrown, this library (when imported) adds a lot of context from the current frame when/where the exception is raised.
Some priorities going forward are stability and segmentation.
Stability is the entire point of what we're trying to accomplish with automated testing. If this goes out the window, why are we writing tests?
In order to attain stability, in a real-world situation, we need to make testing stupid-simple, easy to execute, and actually cover what we think it covers. In order to do that, some of us need to sink some effort into setting up our testing harness. This means limiting things to a specified set of interfaces that we test once in the process (maybe not automated?) and assume it's good in every other section that uses it.
This is where mocking/stubbing/faking comes in. That assumption of successfully calling an external library and getting one of an expected set of responses back can be handled with mocks, for instance. Right now we're looking at Mock
and MagickMock
, but (at the time of writing) have yet to implement either.