Automated testing with Ruby on Rails - best practices

Curious, what are you doing in terms of automating your unit tests with ruby ​​on rails? Do you create a script that runs a rake in cron and does it send you the results? git pre-commit hook? just manual handling? I fully understand the tests, but I wonder what are the best methods to catch errors before they happen. Let it be understood that the tests themselves are flawless and work as they should. What is the next step to make sure they reach you with potentially harmful results at the right time?

+5
source share
2 answers

I'm not sure what exactly you want to hear, but there are several levels of automatic code base management:

  • While working on a function, you can use something like autotest to get instant feedback on what works and what doesn't.

  • To ensure that your transactions really don't break anything, use a continuous integration server like cruisecontrolrb or Integrity (you can bind them to post-commit hooks on your SCM system).

  • Use some kind of exception notification system to catch any unforeseen errors that may appear during the production process.

  • , ( ), - Rackamole.

, .

+8

, . . , . - , - , , .

-, teamcity, . , , . , ( ) - .

- . , IM, IRC, RSS, SMS ( ).

0

All Articles