[ https://issues.apache.org/jira/browse/DERBY-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-1342:
--------------------------------------
Attachment: derbyall_diff.txt
derbyall_pass.txt
derbyall_fail_analysis.txt
DERBY-1342_testoutput.zip
In a first step to move this issue further, I'm attaching the ._pass.txt file of a test run
of derbyall with -Dframework=DerbyNetClient, the _diff.txt file of the same, my analysis of
the failures as notes in the _fail.txt file, and a zip file with the .out, .tmpmstr, .diff,
and derby.log of those differences I thought were worth a closer look.
I'd appreciate it if someone else could take a look at those differences I've marked with
=> in the _fail.txt file.
> 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: Sub-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
|