At Harmonypark we love writing automated tests for our code - our main weapons of choice being RSpec and Cucumber. Something that goes hand-in-hand with good unit testing practices is continuous integration.
Continuous integration is a fancy way of saying that at any given time, your source code (also known as 'the build') should work. In order to verify that the build works, you need to have an automated system to run all of your tests.
This is good for a couple of reasons:
1) You can have faith that the code is always in excellent condition, and good enough to deploy.
2) It ensures that developers are running the automated tests as often as possible.
Because at Harmonypark all the servers we use are in the cloud, setting up a continuous integration server would prove to be a bit problematic.
Enter RunCodeRun.Whenever we check in our code, RunCodeRun runs all of our specifications and features to make sure the commit didn't break anything.
If RunCodeRun runs the tests and finds a failure, an email is sent out to everyone at Harmonypark. This leads to much derision and good-natured name-calling - sometimes tears.
Once the build is fixed, RunCodeRun sends out another email notifying everyone of the fix, and the offending developer breathes a sigh of relief.
Setting up RunCodeRun was pretty straight forward too, as it supports github straight out of the box. You just need to tell RunCodeRun where your github repo is and...BOOM! Instant Continuous Integration!
RunCodeRun is free for open source projects that are on github.
Comments