[mapserver-dev] cunit / RFC 12

Paul Ramsey pramsey at cleverelephant.ca
Mon Nov 10 15:43:54 EST 2008


Frank,

Not a problem, I have my test cases off to the side and can continue
to work on them for my own purposes without needing to commit them to
get utility out of my own little test suite.

P.

On Mon, Nov 10, 2008 at 12:31 PM, Frank Warmerdam <warmerdam at pobox.com> wrote:
> Paul Ramsey wrote:
>>
>> Devs,
>>
>> As I work through the postgis driver, I'm wanting to test individual
>> components of it (data defn parsing, SQL generation, geometry parsing,
>> etc), without invoking a whole Mapserver run... sort of like unit
>> testing. I might just write a wee program to do that, but I was
>> wondering if a more formal approach is worth pursuing?
>>
>> I see RFC 12 brought cunit to the plate, but that's as far as it went.
>> Certainly, getting coverage of the code base this late in the game is
>> going to be hard/impossible, but for new functionality, it has to be
>> useful to have some unit tests in place as one works, no?
>>
>> http://mapserver.gis.umn.edu/development/rfc/ms-rfc-12/
>>
>> Any interest / disinterest in pursuing this?
>
> Paul,
>
> My preference remains to test specific functions as part of a larger
> operations since we already have such technology in place (ie. msautotest)
> or to expose the functionality through mapscript and use mapscript tests
> like Sean's python unit tests.
>
> I do not feel that introducing another testing methodology into the
> project would be wise.
>
> Best regards,
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | Geospatial Programmer for Rent
>
>


More information about the mapserver-dev mailing list