Hi Dharshana, I think soft asserts are more useful in UI automation. We can do our own soft assert implementation using testNG TestListenerAdapter by combining verification failures. However need to be careful on test execution time with soft asserts, because each soft assert trend to do extra work which could increase test execution time.
Thanks, Krishantha. On Thu, Aug 1, 2013 at 11:18 AM, Dharshana Warusavitharana < [email protected]> wrote: > Hi All, > > Currently The WSO2 Test Framework uses only Hard Asserts to verify the > output of the test. > But if we have the support to have soft asserts we can differentiate > verifications and asserts within the test. > > Basically on soft assert/ verification what happens is it will log the > failure but not abort the test. This would be a good addition when we are > running > 1. Lengthy test suites with many test methods. > 2. Avoid and minimize number of tests skipped because of minor issues. > 3. Still we can add more asserts and log many minor failures. > > This would be especially useful in UI automation to verify outer scope > functions and Assert function failures please refer [1]. > > This is not something testing directly supporting but we can implement > this minimal effort. > > [1]. http://beust.com/weblog/2009/06/25/soft-asserts/ > > Thank You, > Dharshana. > -- > > Dharshana Warusavitharana > Senior Software Engineer , Test Automation > WSO2 Inc. http://wso2.com > email : [email protected] <[email protected]> > cell : +94772202595 > blog : http://dharshanaw.blogspot.com > > lean . enterprise . middleware >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
