Re: Airavata unit tests - Mocking

2018-02-28 Thread Sachin Kariyattin
Hi Dimuthu, Not sure about that. I had just used this before during my previous internship. They do have frequent releases and active contributions going on. http://jmockit.github.io/changes.html On Wed, Feb 28, 2018 at 2:20 PM, DImuthu Upeksha wrote: > Hi Sachin, > > +1. mockito also is widely

Re: Airavata unit tests - Mocking

2018-02-28 Thread DImuthu Upeksha
Hi Sachin, +1. mockito also is widely used in the industry. But when I went through some reviews, seems jmockit wins the competition. Do you have an idea about the maturity of the project? [1] http://site.mockito.org/ On Wed, Feb 28, 2018 at 2:14 PM, Christie, Marcus Aaron wrote: > +1. > > > O

Re: Airavata unit tests - Mocking

2018-02-28 Thread Christie, Marcus Aaron
+1. On Feb 27, 2018, at 8:09 PM, Sachin Kariyattin mailto:sachin9...@gmail.com>> wrote: Hello Dev, I see that we don’t use mocking in any of the Airavata unit tests. This sometimes makes it difficult because all the dependent objects need to be created before one particular piece can be teste

Re: Airavata unit tests - Mocking

2018-02-28 Thread Chathura Herath
Tuesday, February 27, 2018 8:09 PM > *To:* dev@airavata.apache.org > *Subject:* Airavata unit tests - Mocking > > Hello Dev, > > I see that we don’t use mocking in any of the Airavata unit tests. This > sometimes makes it difficult because all the dependent objects need to be

Re: Airavata unit tests - Mocking

2018-02-28 Thread Pierce, Marlon
?+1, very good suggestion. Marlon From: Sachin Kariyattin Sent: Tuesday, February 27, 2018 8:09 PM To: dev@airavata.apache.org Subject: Airavata unit tests - Mocking Hello Dev, I see that we don't use mocking in any of the Airavata unit tests. This some

Airavata unit tests - Mocking

2018-02-27 Thread Sachin Kariyattin
Hello Dev, I see that we don’t use mocking in any of the Airavata unit tests. This sometimes makes it difficult because all the dependent objects need to be created before one particular piece can be tested. I came across this when I tried to test the validator class (BatchQueueValidator, GroupRe