[
https://issues.apache.org/jira/browse/DERBY-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2031:
-----------------------------------
Attachment: derby-2031-1a-grammar_enum.stat
derby-2031-1a-grammar_enum.diff
'derby-2031-1a-grammar_enum.diff' adds a grammar enum, describing the "protocol
test language". There is no description of the arguments each command take.
My plan is to convert TestProto to a package-private test first. We can decide
what to do with it later.
I have chosen to use Java SE 5.0 features for this test. Note that the test is
being run today as part of derbyall (testProtocol), and my work on this issue
will not affect that.
Besides from the test conversion itself, I know there are some issues:
a) Security manager (permissions, different codebase)
b) Only runnable from classes (sealing, packaging, special VM options)
> Convert derbynet/testProtocol.java to JUnit
> -------------------------------------------
>
> Key: DERBY-2031
> URL: https://issues.apache.org/jira/browse/DERBY-2031
> Project: Derby
> Issue Type: Improvement
> Components: Network Server, Test
> Affects Versions: 10.3.1.4
> Reporter: Knut Anders Hatlen
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: d2031.diff, d2031.stat, derby-2031-1a-grammar_enum.diff,
> derby-2031-1a-grammar_enum.stat
>
>
> testProtocol.java executes DRDA commands from a file written in a
> special-purpose language. The statements are very much like assertions, so it
> should be fairly easy to convert the test to JUnit.
> Suggested approach: Change the interpreter (TestProto.java) so that is uses
> Assert.fail() instead of System.err.println() and System.exit(), and
> BaseTestCase.println() instead of System.out.println(). It should also use
> TestConfiguration to get the host name and port number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
