db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Commented: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures.
Date Thu, 27 Oct 2005 16:10:19 GMT
John Embretsen wrote:

> Rick Hillegas wrote:
> 
>> Myrna van Lunteren (JIRA) wrote:
>>
> 
> [snip]
> 
>>> Finally I also wondered if maybe these tests ought to be not under
>>> org/apache/derbyTesting/functionTests/tests/compatibility, but under
>>> org/apache/derbyTesting/JUnitTests/compatibility...
>>>  
>>>
>>
>> I don't have strong religion about these points either. Concerning the
>> last issue: I agree that a JUnitTests fork in the tree might help us
>> track which of our existing tests we've migrated under JUnit.
>>
> 
> I agree, I think we could avoid a lot of potential confusion regarding
> Derby testing in the future by having (from the start) an easy way to
> see which tests are written for JUnit and which are not, especially as
> more JUnit-based tests are added. Forking the derbyTesting source tree
> might be a good way to do this - at least I cannot come up with any
> better ideas at the moment.

Do you mean forking, or just a separate directory structure within
derbyTesting?

Forking means a copy of the tree developed independently, not sure why
we would want to go down that path.


Dan.


Mime
View raw message