I agree. I think this is the right approach to test multiple interface abstracted framework like this. +1.
On Wed, Feb 28, 2018 at 8:32 AM Pierce, Marlon <[email protected]> wrote: > +1, very good suggestion. > > > Marlon > ------------------------------ > *From:* Sachin Kariyattin <[email protected]> > *Sent:* Tuesday, February 27, 2018 8:09 PM > *To:* [email protected] > *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 > created before one particular piece can be tested. > > I came across this when I tried to test the validator class > (BatchQueueValidator, GroupResourceProfileValidator etc). > > I am Planning to use JMockit http://jmockit.github.io and implement a > unit test to start with. Any feedback/views on this is appreciated. > > > -- > > > *Regards, Sachin Kariyattin * > -- Chathura Herath Ph.D. https://www.cs.indiana.edu/~cherath/ http://chathurah.blogspot.com/
