I build tools to manage large Rails deployments all day long. Not a bad job, eh?
Before we get into monitoring or cucumber, let&#x2019;s talk about testing.
In my career as a dev, my testing habits have evolved over time, largely inspired by available tools.
I&#x2019;m sure some of you have shared a similar journey - let&#x2019;s take a quick look back.
Save in your editor / refresh in your browser / lather / rinse repeat.
Occasional human preformed quality assurance
Broken by design
Basically, BDD nirvana. Stakeholder-*writable* if you&#x2019;re crazy.
For those of you that aren&#x2019;t familiar with Cuke
But what about production? We&#x2019;re testing all the time in development, while we&#x2019;re developing the that&#x2019;s going to create revenue. But in production...
...there&#x2019;s actually revenue being earned. Why not test with the same veracity in production?
Search can fail when the rest of a site works fine due to many reasons:
* search daemon may go down * the indicies may be corrupt * or things may fail in a more interesting kind of way...
Pingdom&#x2019;s a relatively new tool that&#x2019;s gained a good bit of traction. It&#x2019;s a hosted monitoring service, that can test HTTP and many other types of services from a network of computers around the world. This covers the availability angle quite well
Cucumber&#x2019;s served well for me in my experience in bringing stakeholders and developers together.
But with a couple quick edits
We have a tool that can help us bring together developers, operations, *and* stakeholders