airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <>
Subject Re: Tests in Airavata
Date Sun, 24 Mar 2013 22:24:50 GMT
Hi Amila,

Ofcourse + 1 for the approach in general. I think you are proposing this at the right time.
This should really help out for GSoC projects. I can clearly see how your wiki document can
be followed and it is easy for both student and mentor to contribute and review. 

I am wondering on practical logistics of employing TDD for Airavata development in general.
Any thoughts? I think if we make it a practice now it will have a long pay off and we are
starting to see code base getting out of control in terms of build breaking.


On Mar 24, 2013, at 1:07 PM, Amila Jayasekara <> 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]
> Thanks
> Amila

View raw message