Archive for the 'Testing' Category

Develop Restful application with RESTeasy

May 7 20096 Commented

Categorized Under: Engroup, Java, Software Engineer, Technology, Testing

Web service is complicated, to understand web service you must know SOAP, WSDL, XML schema etc. CORBA is even more completed than Web service. Our team have many years experience of developing web services by using various libraries like Axis, XFire and Cxf .We spent nearly month to understand and practice each type of SOAP [...]

Testing Spring beans against database with DbUnit

April 5 2009one Commented

Categorized Under: Agile, Engroup, Java, Software Engineer, Technology, Testing

This is another post of testing series we wrote so far and it discusses how to write testing against database. We prefer writing unit test for whole kind of our services, it includes the testing against POJO, LDAP, database, content repository, email. Here the topics relate to testing in our site:

Some questions and answers of [...]

Integration of Jackrabbit OCM and Spring (updated version)

March 26 20097 Commented

Categorized Under: Engroup, Java, Object Oriented and Design, Technology, Testing

In the previous post Jackrabbit OCM and Spring, I have outlined the way of integrating between Jacckrabbit OCM (jackrabbit 1.5.0-snapshot) and Spring. The time flies help us have more JCR knowledge, jackrabbit api becomes more stable and our Engroup ECM implementation is changed. Instead of creating the total new JCR node types for our domain [...]

Unitils – library for enhance unit test by using annotation approach

October 16 2007No Commented

Categorized Under: Agile, Java, Testing

In the post Enhance the Unit test using Annotation approach, I outlined the approach of using annotation to reduce the redundant code and avoid the inheritance (like JUnit3). Annotation RunWith of JUnit4 is a powerful class help us to custom the approach of running unit test, we can create the class inherits from class TestRunner. [...]

Unit test – Best practices

September 5 2007one Commented

Categorized Under: Agile, Software Engineer, Testing

1. Keep test method as simple as possible:

DRY principle (Don’t repeat yourself)
Re-use test set up across test cases: put non-trivial test data in test set up method
Clean test code as productive code