[
https://issues.apache.org/jira/browse/DERBY-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll updated DERBY-3203:
----------------------------------
Attachment: DERBY-3203v3.diff
Hi Ramin,
I think Dan is making a very good point about the missing fail()
asserts in some of the try-blocks.
I've attached a patch (v3) which adds the missing fail()-asserts.
Unfortunately, it also reveals that one of the test
cases is not throwing the expected exception :(
The statement that doesn't fail is 'rs.setFetchSize(100)' in
'testLocalValuesOfResultSet()' in client mode. In v3 I have
enclosed the fail()-assert in an usingEmbedded()-test just to
make the test pass, but I don't know if this is expected
behavior or a bug. What do you think?
> Convert jdbcapi/statementJdbc20.java to JUnit
> ---------------------------------------------
>
> Key: DERBY-3203
> URL: https://issues.apache.org/jira/browse/DERBY-3203
> Project: Derby
> Issue Type: Test
> Reporter: Ramin Moazeni
> Assignee: Ramin Moazeni
> Fix For: 10.4.0.0
>
> Attachments: DERBY-3203v0.diff, DERBY-3203v0.stat, DERBY-3203v2.diff,
> DERBY-3203v3.diff
>
>
> This issue is creates for converting jdbcapi/statementJdbc20.java to JUnit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
