[Pywps-dev] Running the unit tests

Alex Morega alex at grep.ro
Fri Jun 21 13:24:20 PDT 2013


Hi Jachym,

I'm referring to pywps-4. It does have a number of unit tests which look useful, even if you decide to change the API, we can refactor them bit by bit. But it would be really good to have the test suite passing at all times, otherwise why bother writing them? :)

Cheers,
-- Alex

On 21 Jun 2013, at 22:53, Jachym Cepicky <jachym.cepicky at gmail.com> wrote:

> Hi Alex,
> 
> welcome on board!
> 
> Are you referring to github/geopython/PyWPS or github/jachym/pywps-4?
> 
> As for the "old" version: it would be great to have it running
> 
> But I would like to focus on the new aka "4" version, which can be done
> from scratch basically anyhow and anywhere. After the discussion we had
> in Bucharest, it's clear to me, that even the little I did is worth to
> be rewritten :-)
> 
> Thanks
> 
> Jachym
> 
> Dne 20.6.2013 23:07, Alex Morega napsal(a):
>> Hello!
>> 
>> There's a nice testing tool, called tox[1], that automates running unit tests against multiple Python versions and configurations. Also, since the project is on Github, we can set up Travis[2] to run the unit tests for every commit and pull request.
>> 
>> I can set up both, but so far I've not been able to run the test suite successfully, either on Python 2.7 or 3.3. Are all the tests up-to-date with the latest commits?
>> 
>> Cheers,
>> -- Alex
>> 
>> [1] http://testrun.org/tox/latest/
>> [2] https://travis-ci.org/
>> 
>> _______________________________________________
>> pywps-dev mailing list
>> pywps-dev at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
>> 
> 
> -- 
> Jachym Cepicky
> Help Service - Remote Sensing s.r.o.
> jachym.cepicky at gmail.com
> HS-RS: jachym at hsrs.cz http://bnhelp.cz
> http://les-ejk.cz
> 



More information about the pywps-dev mailing list