[ADD] Added test case to check the resource calandar fucntion

bzr revid: jam@tinyerp.com-20111129053602-nf19mwtk8ya19ahi

addons/resource/__openerp__.py

@@ -47,6 +47,7 @@ It also manages the leaves of every resource.
     ],
     'test': [
                 'test/process/test_resource.yml',
+                'test/process/test_resource_calendar.yml',
                 'test/ui/on_change_resource.yml',
                 'test/ui/duplicate_resource.yml',
             ],

addons/resource/test/process/test_resource_calendar.yml

@@ -0,0 +1,29 @@
+-  | 
+  In order to test resource calendar, I use the Demo record '38 Hours/Week'.
+-
+  I check the working hour on day for resoruce 'Demo Resource' using calendar '38 Hours/Week' .
+-
+  !python {model: resource.calendar}: |
+    from datetime import datetime
+    dt = datetime.now()
+    calendar = self.browse(cr, uid,  ref('timesheet_group1'))
+    result = self.working_hours_on_day(cr, uid, calendar, dt, context)
+    assert result, "No Working Our on Day for Resource has been Generated."
+-
+  I Check the Resource 6.0 Hours Working Internal Timeming Based on Resource Calendar.
+-
+  !python {model: resource.calendar}: |
+    from datetime import datetime
+    dt = datetime.now()
+    result = self.interval_get(cr, uid, ref('timesheet_group1'), dt, 6.0)
+    assert result, 'No Working Internal Timeming Generated'
+    
+-
+  I check total number of working hours on resource in between three dates based on resource working calendar.
+-
+  !python {model: resource.calendar}: |
+    from datetime import datetime, timedelta
+    dt_from = datetime.now()
+    dt_to = dt_from  + timedelta(days=3)
+    hours = self.interval_hours_get(cr, uid, ref('timesheet_group1'), dt_from, dt_to)
+    assert hours, 'No Working Hours Generated'