IMO, its good if we can adopt TDD (Test Driven Development), where we starts with a failing test case, then add production code to pass the test case using refactoring tools provided by IDE s, and keep adding more test cases. More scenarios can be covered in this approach.
Also, sometime back I came to know about a test framework named Cucumber [1], which seemed interesting (but couldn't try out yet), which allows developers to write test cases in plain text, as behaviours. [1] http://cukes.info/ Thanks, Sajith On Fri, Jun 15, 2012 at 9:38 AM, Suhothayan Sriskandarajah <[email protected]>wrote: > > Thanks > Sure, it also helped me for tuning performance by doing some load test. > The instructions for the load test can be found here[1] > > Suho > > [1] > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/agent/org.wso2.carbon.agent.server/src/test/README.txt > > > > On Thu, Jun 14, 2012 at 7:22 PM, Srinath Perera <[email protected]> wrote: > >> absolutely +1, I have written single JVM node tests for systems that have >> 100+ servers .. It is bit of work, but pays off as hell at the end >> >> --Srinath >> >> On Thu, Jun 14, 2012 at 6:42 PM, Tharindu Mathew <[email protected]>wrote: >> >>> I've seen some good unit tests for the Agent API from Suho, and it has >>> resulted in some solid code. >>> >>> If you write good unit tests you get the following advantages: >>> >>> - You don't have to build other components to figure out basic >>> functionality has broken. >>> - The code naturally improves using proper interfaces to accomodate unit >>> tests. >>> - If basic functionality is broken you know immediately. >>> - You do not need to write features, copy/paste jars in dropins to know >>> whether your code works properly. >>> >>> So I'd like to encourage *EVERYONE* to write some good unit tests just >>> like Suho has written. >>> >>> The tests are at >>> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/agent/org.wso2.carbon.agent.server/src/test/java >>> >>> -- >>> Regards, >>> >>> Tharindu >>> >>> blog: http://mackiemathew.com/ >>> M: +94777759908 >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> http://www.cs.indiana.edu/~hperera/ >> http://srinathsview.blogspot.com/ >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *S. Suhothayan > * > Software Engineer, > Data Technologies Team, > *WSO2, Inc. **http://wso2.com > <http://wso2.com/>* > *lean.enterprise.middleware.* > > *email: **[email protected]* <[email protected]>* cell: (+94) 779 756 757 > blog: **http://suhothayan.blogspot.com/* <http://suhothayan.blogspot.com/> > * > twitter: **http://twitter.com/suhothayan* <http://twitter.com/suhothayan>* > linked-in: **http://lk.linkedin.com/in/suhothayan* > * > * > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Sajith Kariyawasam* *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
