[ 
http://issues.apache.org/jira/browse/DERBY-1303?page=comments#action_12413716 ] 

Kristian Waagan commented on DERBY-1303:
----------------------------------------

Hello Tomohito,

I had a look at the SuicideOfStreaming test. In my opinion, more can be done to 
make it more "JUnit friendly".
That said, I also observe that our JUnit environment lacks some supporting 
functionality. I might take some time to work on the test, but first I have a 
few questions.

1) Is the test supposed to be runnable through it's main method?

2) Do we need support for starting, and shutting down, a network server from a 
JUnit test?
Where should this functionality be placed? As a subclass of BaseJDBCTestCase, 
or in an independent/existing utility class?
Two cases:
a) In same process; is doable. If things go wrong, server dies with the VM.
b) In separate process; more complicated. If the test hangs/fails the server 
process can be left running. This is similar to the existing NetServer, but 
here server management is done by the harness, not the test process itself 
(exception; useprocess=false).

3) Can someone confirm or deny that we have recommended to place JUnit tests in 
the same directory structure as the other tests?

I know of two JUnit tests that require a server to be explicitly started and 
manipulated "outside the harness": SuicideOfStreaming and the tests for 
Connection.isValid().

> The test of derbynet/SuicideOfStreaming.java is failed when programs are 
> build as Insane.
> -----------------------------------------------------------------------------------------
>
>          Key: DERBY-1303
>          URL: http://issues.apache.org/jira/browse/DERBY-1303
>      Project: Derby
>         Type: Bug

>   Components: Test
>  Environment: 
> http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/Limited/testSummary-405038.html
>     Reporter: Tomohito Nakayama
>     Assignee: Tomohito Nakayama
>  Attachments: DERBY-1303.patch
>
> "derbynet/SuicideOfStreaming.java" have dependency on build as Sane.
> When programs are build as Insane, 
> code to cause artificial Exception is not compiled and 
> streaming does not failed in derbynet/SuicideOfStreaming.java as expected in 
> this test program.
> The dependency results in fail of derbynet/SuicideOfStreaming.java when 
> programs are comiled as insane.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to