Hi,
I don’t know if this is “best practice”, but you could do this using mocking if nothing else. Cheers, Jens ——— Jens Rantil Backend engineer Tink AB Email: jens.ran...@tink.se Phone: +46 708 84 18 32 Web: www.tink.se Facebook Linkedin Twitter On Tue, Dec 9, 2014 at 8:42 PM, Clint Kelly <clint.ke...@gmail.com> wrote: > Hi all, > I'd like to write some tests for my code that uses the Cassandra Java > driver to see how it behaves if there is a read timeout while accessing > Cassandra. Is there a best-practice for getting this done? I was thinking > about adjusting the settings in the cluster builder to adjust the timeout > settings to be something impossibly low (like 1ms), but I'd rather do > something to my test Cassandra instance (using the > EmbeddedCassandraService) to temporarily slow it down. > Any suggestions? > Best regards, > Clint
