aghyad · December 20, 2013 17:32
diff --git a/testing_rake_tasks.txt b/testing_rake_tasks.txt
 So you like to write some complicated tests plugged into your rake tasks. Or may be you think you're doing a crime not doing so. I understand. Nothing is wrong with that. But it's more like buying a helicopter so you can travel two blocks in Manhattan.

 I'll explain:

 1 - Rake tasks are not meant to be a complicated piece of your website. Instead, rake tasks are meant to be "thin" and only to invoke other modules in your system. Those modules do the heavy work. Those modules are what really matters. So, test the meaningful code and not the code that invokes it. Well, if you are still feeling unconfident about the invoking processes ... then:

 2 - Trust rails and trust the whole framework. Don't bother testing whether this rake task is going to print something minor. It will work. Otherwise, you have a bigger issue that missing tests in the framework. 

 In summary: Focus your energy more on testing the functionality that this rake task is written to invoke, which is a class or a method some where else in your models or lib files or any where else. 

 Otherwise, your website will start killing kittens and choking birds for no reason! - not that there's a reason anyway to kill or choke kittens and birds :)

 Don't be mad - I'm just sayin'
	So you like to write some complicated tests plugged into your rake tasks. Or may be you think you're doing a crime not doing so. I understand. Nothing is wrong with that. But it's more like buying a helicopter so you can travel two blocks in Manhattan.

	I'll explain:

	1 - Rake tasks are not meant to be a complicated piece of your website. Instead, rake tasks are meant to be "thin" and only to invoke other modules in your system. Those modules do the heavy work. Those modules are what really matters. So, test the meaningful code and not the code that invokes it. Well, if you are still feeling unconfident about the invoking processes ... then:

	2 - Trust rails and trust the whole framework. Don't bother testing whether this rake task is going to print something minor. It will work. Otherwise, you have a bigger issue that missing tests in the framework.

	In summary: Focus your energy more on testing the functionality that this rake task is written to invoke, which is a class or a method some where else in your models or lib files or any where else.

	Otherwise, your website will start killing kittens and choking birds for no reason! - not that there's a reason anyway to kill or choke kittens and birds :)

	Don't be mad - I'm just sayin'