airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lahiru Gunathilake <>
Subject Re: Writing until tests and using properties from
Date Sat, 12 Apr 2014 04:06:09 GMT
If you don't have credentials you just have to run with default profile
which will skip all the test cases which require credentials.

Once I am done implementing until tests I will send an email with


On Sat, Apr 12, 2014 at 12:00 AM, Sachith Withana <>wrote:

> Lahiru,
> What happens when the unit tests are run without those properties being
> set? ex: myproxy.password is not check?
> On Fri, Apr 11, 2014 at 3:25 PM, Lahiru Gunathilake <>wrote:
>> Hi Devs,
>> During unit test writing, we need some of the properties to be set and
>> currently in airavata we have in only one place.
>>  When we retrieve them from and we
>> give higher preference to the system property with the same key and then we
>> read from
>> So during until test writing we can use this feature and set your
>> required properties in your test case and use them. If there are properties
>> which needs to be provided by the person who run the tests (ex: myproxy
>> password, certificate location) we can read these from maven system
>> property setting like below.
>> mvn clean install -Dmyproxy.password=xxx.
>> I have finished the tests cases for gsissh,job-monitor,orchestrator-core
>> and gfac-core using the the above mentioned model. With this approach we do
>> not need to duplicate all over the modules.
>> Meantime we can have a test for our sample
>> airavata-server/ files to check whether our sample
>> properties file we ship is syned with the code which reads them.
>> Regards
>> Lahiru
>> --
>> System Analyst Programmer
>> PTI Lab
>> Indiana University
> --
> Thanks,
> Sachith Withana

System Analyst Programmer
Indiana University

View raw message