[MetaCRS] Directory structure for CSV Test data files

[Norm Olsen]

I'm not sure I understand much of this about SVN and Java conventions, skip lists,  etc.

I'd like to see the maintenance of this test database, and others which may follow, as a separate project with its own Trac.  Hopefully, there will be very few changes to the actual test cases other than additions; but if such a change ever became necessary, I think it important to be able to find the documentation on the change quickly and easily.

I also see this database as a valuable resource for projects other than the ones we manage; and would welcome and encourage well documented additions provided (to us in the community) by those outside the community.

Norm


-----Original Message-----
From: metacrs-bounces at lists.osgeo.org [mailto:metacrs-bounces at lists.osgeo.org] On Behalf Of Martin Davis
Sent: Monday, November 16, 2009 12:29 PM
Cc: metacrs at lists.osgeo.org
Subject: Re: [MetaCRS] Directory structure for CSV Test data files

I agree with Martin - the Test Suite should follow the common SVN and 
Java conventions.  Even if they are not actually contributing much to 
the "build", it makes the project structure familiar.  It's easy to 
trace through the structure to find the actual data files.

I expect that each project will obtain a copy of the relevant files 
during its development and test phases, rather than at build or deploy 
time.  I suspect each lib will have different "response patterns" to the 
test suite, and may require some tailoring of the suite (or more 
preferably the definition of a skip list) to avoid continual reporting 
of known failures. 

Martin D2

Martin Desruisseaux wrote:
> Hello all
>
> The "trunk" folder was proposed for complying with the common practice 
> of projects on SVN. All projects in http://svn.osgeo.org/metacrs/ 
> except sr.org declare such folder. We don't have to do the same and I 
> don't really mind. But we could imagine that at some point in the 
> future, we wish to change the file format and maintain a branch for 
> the projects that are not ready to update their parser, in which case 
> a "branches" folder would follow SVN practices.
>
> However we could do the same with just a second file in the same 
> directory, so I'm actually neutral.
>
>     Regards,
>
>         Martin
>
>
>
> Norm Olsen a écrit :
>> Don't we already have a directory "testsuite" at the root.  I don't 
>> imagine folks reading the file directly from the web.  Obtaining the 
>> test file would be part of their download procedure and they put it 
>> where they need it.
>>
>> You don't get to a "trunk" folder until you've selected a library.  
>> The purpose of this file is to be completely independent of the 
>> specific library in use, is it not???
>>
>> Norm
>
> _______________________________________________
> MetaCRS mailing list
> MetaCRS at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/metacrs
>

-- 
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022

_______________________________________________
MetaCRS mailing list
MetaCRS at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/metacrs