[Pywps-dev] pywps-4 and ogc cite tests

[Jachym Cepicky]

When the test fails, you can see the request in the detail of it (View
details link)

J

út 7. 7. 2015 v 16:35 odesílatel Luís de Sousa <luis.a.de.sousa at gmail.com>
napsal:

> Hi Jachym,
>
> Is there a way to see the precise request used for each test? I would
> like to register these failures as issues at GitHub.
>
> Another thing: the tests did not run on Firefox, I had to use Chromium.
>
> Cheers,
>
> Luís
>
> On 6 July 2015 at 02:58, Tom Kralidis <tomkralidis at gmail.com> wrote:
> > Hi Jachym: glad to see this!  Giving experience from pycsw, the CITE
> tests are
> > an invaluable resource to ensuring compliance over the long term.
> >
> > I'm not familiar with ets-wps10, but for the CSW case we work with all
> CSW
> > test suites on the command line to build and execute tests
> automatically.  This
> > also makes it very straightforward to run the CITE test as part of a
> travis-ci
> > setup.  I'm guessing similar functionality might be available in CITE WPS
> > which would make your test/investigate/fix cycle much easier.
> >
> > ..Tom
> >
> >
> > On Sun, Jul 5, 2015 at 8:40 PM, Jachym Cepicky <jachym.cepicky at gmail.com>
> wrote:
> >> Hi all,
> >>
> >> after successful deployment of PyWPS-4 on the server (for playing
> around you
> >> can use pywps.cloudapp.net), I've started to have a look at OGC Cite
> tests.
> >> The result is not so good, we have to work on it a bit.
> >>
> >> If you wanna help,
> >>
> >> 1 - you have to go to http://cite.opengeospatial.org/te2/
> >>
> >> 2 - at the bottom of the page, you have to sign in
> >>
> >> 3 - create testing session
> >>
> >> 4 - fill the url of PyWPS instance
> >>
> >> 5 - have a look at bugs, fix on the server (apparently, you can not do
> this
> >> for pywps.cloudapp.net  and localhost dost not help
> >>
> >> 6 - start the whole testing session again (you have to perform all the
> steps
> >> by hand again, reloading does not help)
> >>
> >> Sofar, I've tested getcapabilities.
> >>
> >> 1 - Metadata should not contain any strings
> >> 2 - processVersion should be filled (and it is  not wps:processVersion
> >> 3 - in the header of the capabilities document, reference to
> DescribeProcess
> >> response xsd is present
> >>
> >> I'll try to make those things work
> >>
> >> Jachym
> >>
> >> _______________________________________________
> >> pywps-dev mailing list
> >> pywps-dev at lists.osgeo.org
> >> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
> > _______________________________________________
> > pywps-dev mailing list
> > pywps-dev at lists.osgeo.org
> > http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20150707/a2ded972/attachment.html>