airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <sma...@apache.org>
Subject Re: [VOTE] Test Driven Development for Airavata
Date Mon, 15 Apr 2013 16:03:18 GMT
Here is my + 1.

We have consensus so far, but since this is a policy, I will leave it open for few more hours
before closing, if you have any disagreements please voice them now.

Cheers,
Suresh

On Apr 10, 2013, at 8:18 AM, Suresh Marru <smarru@apache.org> wrote:

> Hi All,
> 
> This was a very good proposal from Amila, there was some discussion but not a lot. How
about we vote on it to make it a policy for the project.
> 
> + 1 Apache Airavata will benefit from TDD and I agree to adopt it as a policy. 
> + 0 I have no opinion
> -1 I think TDD development make hinder creativity ..or I disagree to make this as a policy
because …...
> 
> Suresh
> 
> On Mar 24, 2013, at 1:07 PM, Amila Jayasekara <thejaka.amila@gmail.com> wrote:
> 
>> Hi All,
>> 
>> As an attempt to increase test coverage we thought of introducing
>> "Test Driven Development" (TDD) into Airavata. Please find more
>> information about how we use TDD in Airavata in [1].
>> 
>> TDD is easy to follow approach with lot of advantages. So we encourage
>> everyone to use TDD in their projects (GSoC and also in regular
>> patches).
>> Further we have developed set of integration tests and feel free to
>> augment integration test coverage. You may also find information about
>> integration tests in [1].
>> 
>> We consider functionality is "completed" when we have a comprehensive
>> test cases which tests those functionality.
>> 
>> Please feel free to comment (good or bad).
>> 
>> [1] https://cwiki.apache.org/confluence/display/AIRAVATA/Tests+in+Airavata
>> 
>> Thanks
>> Amila
> 


Mime
View raw message