Will Read's blog
In any consulting job, a project truly fails when expectations are not clearly communicated. In Ruby, we have a great tool for communicating expectations about code. What if we applied that same tool to real life? The anchors at Pivotal Labs have a wealth of knowledge about what elements contribute to a smooth running project. I have my own ideas about what makes a project fun to work on. Below is a very short start to what I like to see about a project going in. This is not to say that a project that fails this spec is "bad", just that I feel a lot better when a project already has these things in place.
This is Part 2 of my two part series on working with queues in Ruby. If you want some context please head over to part 1. In this post I'll touch on Moqueue, using RSpec to stub out Bunny, and a few other hurdles along the way.
Q: How do you catch a unique rabbit?
A: Unique (you-neek) up on it!
Q: How do you catch a tame rabbit?
A: Tame way!!!!!
We've been using RabbitMQ as a queue server, alongside the clients, Bunny, and AMQP. In this series I'm hoping (hopping?) to show you some of the pitfalls we've learned to avoid and talk about how to write tests that test your code without getting stuck running a queue server in your test environment.
In Part 1 I'll focus on our situation and creating some context around our choices so that you can decide what makes sense for your project. In Part 2, I'll get into the nitty gritty of how to write some tests/specs around your queues.