db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-779) Add tests from derbylang to derbynetclientmats suite
Date Mon, 20 Oct 2008 18:01:44 GMT

     [ https://issues.apache.org/jira/browse/DERBY-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren resolved DERBY-779.
--------------------------------------

    Resolution: Won't Fix

I'm marking this as won't fix, because we're now adding tests to be run with networkserver
by adding appropriate run instructions in the junit suites.

> Add tests from derbylang to derbynetclientmats suite
> ----------------------------------------------------
>
>                 Key: DERBY-779
>                 URL: https://issues.apache.org/jira/browse/DERBY-779
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Deepa Remesh
>            Assignee: Deepa Remesh
>            Priority: Minor
>
> I ran derbyall by adding derbylang suite to derbynetclientmats. Most of the tests needed
new masters with client driver. I found that test coverage did not increase much whereas time
to run derbyall increased by ~75 minutes. Here is the increase in test coverage from EMMA:
> org.apache.derby.client.am : 1% method and block coverage
> org.apache.derby.client.net : 2% block and line coverage
> org.apache.derby.jdbc.ClientDriver.java : 4% block and 2% line coverage
> 	
> Instead of adding the whole suite, I think I will look at classes/methods which are not
covered and see which tests can be added from derbylang to improve test coverage.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message