axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (Commented) (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5239) Upgrade Axis2 to use xmlschema2
Date Tue, 20 Mar 2012 19:45:50 GMT


Andreas Veithen commented on AXIS2-5239:

At some point I started the migration to XmlSchema 2.0, but gave up after a couple of changes
because of the missing test coverage [1]. On the other hand, the branch that upgrades Woden
(which is a dependency of Axis2) to XmlSchema 2.0 still exists [2].

Obviously it is not a good strategy to randomly start writing test cases. Instead, we need
to figure out which parts of the code have test coverage and which parts don't. There are
only two strategies for that:

1. Examine the commits that added the code and check if a test case was included. That is
how I checked some of the code when I started the modifications for XmlSchema 2.0, but it's
neither an effective nor an efficient strategy.

2. Measure the code coverage. There are tools for that, but it is not as easy as it sounds.
E.g. with Cobertura it is possible to get a test coverage report for a Maven project with
a single command (mvn cobertura:cobertura), but it only measures the test coverage generated
by the unit tests in the same Maven module. In Axis2 this would largely underestimate the
test coverage because we have two big Maven modules (jaxws-integration and integration) that
contain integration tests for the other modules. Maybe Clover works better in multi-module
builds. Note that Clover is a commercial product but there is a free license for Apache projects.

> Upgrade Axis2 to use xmlschema2 
> --------------------------------
>                 Key: AXIS2-5239
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>            Reporter: Sagara Gunathunga 
>              Labels: axis-gsoc, gsoc2012
> This involves writing some test coverage for existing xmlschema features and porting
to new xmlschema2 API.   

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message