[Building Sakai] Suggestion: Promote test-harness to kernel

David Horwitz david.horwitz at uct.ac.za
Fri Oct 9 11:59:46 PDT 2009


Hi Beth,

This has the advantage of rationalizing our dependency tree - without it
(or an independent test-harness) release any component that uses test
harness must be released in lock step with the whole Sakai release....

D

Beth Kirschner wrote:
> Well, the code is lightweight and stable -- it hasn't effectively
> changed in years, so this seems like a reasonable request. But I'd
> like to know if there are other reasons beyond convenience to include
> it in the kernel?
>
> - Beth
>
> On Oct 9, 2009, at 5:52 AM, Steve Swinsburg wrote:
>
>> If this is 'the' way to run integration tests for Sakai apps, then +1.
>>
>> cheers,
>> Steve
>>
>>
>> On 09/10/2009, at 6:53 PM, David Horwitz wrote:
>>
>>> Hi All,
>>>
>>> A dependency uncovered during our 2.7 looking work is test harness.
>>> This
>>> is a jar that is depended on from multiple locations at test scope,
>>> has
>>> only dependencies on the kernel. It would seem sensible that this is
>>> incorporated into the kernel release - thoughts?
>>>
>>> David
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org
>>> with a subject of "unsubscribe"
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>>
>


More information about the sakai-dev mailing list