[pgrouting-dev] Testing infrastructure?

Hi Mapserver Devs,

I am working on making changes to pgRouting and one of the things we need to put in place is some testing infrastructure.

Looking for some Doc on this I found:

http://mapserver.org/development/tests/autotest.html

this seems to be dated because it is talking about svn and not git. Is it still valid?

I thought Thomas set up a build bot that built and tested on multiple systems, but I'm drawing a blank on that. Can you point me to some links for how to do that. Also is it possible to get the build bot to do windows builds using MinGW/MSYS, if you know?

Thanks,
   -Steve

Thomas and Tamas,

Thank you, that was what I needed. I'm not quite ready to dive into this yet as I need to do more research but I'll start reading up on it and look at what you have done.

I think the biggest challenge for pgrouting will be setup up the test cases to start with.

Thanks,
   -Steve

On 3/7/2013 5:48 AM, Tamas Szekeres wrote:

2013/3/7 thomas bonfort <thomas.bonfort@gmail.com
<mailto:thomas.bonfort@gmail.com>>

     >
     > I thought Thomas set up a build bot that built and tested on multiple
     > systems, but I'm drawing a blank on that. Can you point me to
    some links for
     > how to do that. Also is it possible to get the build bot to do
    windows
     > builds using MinGW/MSYS, if you know?
    I'll let Tamas comment on the windows part.
    For linux, the testsuite could be run on travis-ci (you can find the
    configuration for it in the .travis.yaml file in our repo). We/I
    switched to using a self hosted jenkins instance as the travis service
    tended to be a bit more unreliable (false positives generated by the
    travis infrastructure rather than our own code) and slower (as the
    system dependencies need to be re-installed for each run. travis runs:
    ~4min30sec; jenkins:~1min30sec)

The Windows buildsystem at http://www.gisinternals.com/sdk/ runs
msautotest as part of the build process. You may inspect the results by
clicking on the msautotest link from the start page.

However I had to disable the wxs tests since it was hanging with all
configurations. This may be due to a memory corruption problem which I
still didn't have the chance to track it down.

Best regards,

Tamas