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] Updated: (DERBY-1342) Run derbyall suite with -Dframework=DerbyNetClient and analyze failures
Date Thu, 17 Feb 2011 20:30:24 GMT

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

Myrna van Lunteren updated DERBY-1342:
--------------------------------------

    Issue Type: Task  (was: Sub-task)
        Parent:     (was: DERBY-209)

> Run derbyall suite with -Dframework=DerbyNetClient and  analyze failures
> ------------------------------------------------------------------------
>
>                 Key: DERBY-1342
>                 URL: https://issues.apache.org/jira/browse/DERBY-1342
>             Project: Derby
>          Issue Type: Task
>          Components: Network Client, Network Server, Test
>    Affects Versions: 10.2.1.6
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: DERBY-1342_testoutput.zip, derbyall_diff.txt, derbyall_fail_analysis.txt,
derbyall_pass.txt
>
>
> In order to expose issues in network client and server it would be good to run the derbyall
suite with DerbyNetClient framework and file Jira Bugs for issues found.  In general I don't
know that it is worth the time added to derbyall and the effort to get the full suite running
without diffs for  client but it certainly would be worthwhile to run the tests and see what
issues they expose.  Java tests and that exposed issues might  be good to add to improve client
coverage.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message