[OSGeo-Standards] OGC client testing

Raj Singh rsingh at opengeospatial.org
Tue Jul 21 18:20:15 EDT 2009


This sounds to me like Open Web Context and/or Web Map Context  
document tests (which we also need). My idea of client testing centers  
on the ability of client-side software to translate a human's actions  
into a service request. Here are some examples:

WMS: client displays layer legend. User turns off a layer. Examine map  
request.
WFS: User draws a bounding box. Client generates a BBOX spatial filter  
request.
etc.

I think humans are inherently in the loop in any client-side testing,  
and all client UIs are different, which is why I'm stumped as to how  
to approach this.

---
Raj


On Jul 16, at 8:33 PM, Jody Garnett wrote:

> I wonder if we can think of something?
>
> Easiest I could think of would be to define client conformance test
> based around Open Web Service Contact documents (and/or Web Map Server
> context documents).
>
> 1. Define a test suite of context documents - each defines the region;
> layers and styling required
> 2. Have an upload (or paste) page for people to upload the screen snap
> of their client
> 3. Process the resulting image with a histogram for the pass/fail
>   (you can use more interesting things like edge detection and so on)
>
> That would be fine for a POC.
>
> For more advanced work you provide one of those visual testing tools
> and ask people to generate you a script to load the context document
> (click the buttons etc) and automate the process of taking the screen
> snapshots etc... but that would be for after a POC.
>
> Is this a good idea for a "Call for Participation"?
>
> Jody
>
> On Fri, Jul 17, 2009 at 5:27 AM, Raj  
> Singh<rsingh at opengeospatial.org> wrote:
>> Hi Dave. Unfortunately I don't have very good answers for you. OGC  
>> has no
>> conformance testing programs for clients. This is a known hole in our
>> offerings, but no one has suggested a clear, cost-effective  
>> strategy for
>> doing client testing. We're open to ideas on this.
>>
>> Also, we don't have a nice way for you to advertise that your product
>> implements OGC standards if it's not certified. Our existing policy  
>> on the
>> use of OGC marks is here:
>> http://www.opengeospatial.org/ogc/policies/trademark/
>>
>> I see that Quantum GIS is an OSGeo project. We have an MOU in place  
>> with
>> OSGeo, and it would be a great contribution if OSGeo could do some  
>> work in
>> this area and suggest some sort of policy in this area.
>>
>> -----
>> Raj Singh
>> Open Geospatial Consortium
>> rsingh at opengeospatial.org
>> +1 (617) 642-9372
>>
>> ** making location count **
>>
>>
>>
>> On Jul 14, at 4:10 PM, Greg Buehler wrote:
>>
>>>
>>>
>>> -------- Original Message --------
>>> Subject:        Use of logo for clickable icon
>>> Date:   Sat, 11 Jul 2009 15:46:17 -0400
>>> From:   Dave Sampson <samper.d at gmail.com>
>>> To:     info at opengeospatial.org
>>>
>>>
>>>
>>> Hey Folks,
>>>
>>> I recently made a couple of plugins for use in QGIS an open source
>>> desktop GIS application.
>>>
>>> During development I just grabbed the three-hexagonal OGC icon  
>>> from the
>>> address bar when visiting the site to use as a place holder.
>>>
>>> After looking at the other logos I feel they might be too large to  
>>> use
>>> for a clickable icon and the product is not yet certified (see  
>>> bellow).
>>>
>>> Since the plugin is a CSW client I am wondering if there might be  
>>> a more
>>> appropriate icon I can use. I also made a GeoRSS plugin but I am  
>>> using
>>> the world icon with the RSS feed icon for the clickable icon and I
>>> assume that is not an OGC trademark.
>>>
>>> About testing our plugins, they are clients. So how do I test a  
>>> client
>>> using CITE. it seems server centric and we are looking for tests to
>>> consume data not serve data.
>>>
>>> Any thoughts?
>>>
>>> Cheers
>>>
>>
>> _______________________________________________
>> Standards mailing list
>> Standards at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/standards
>>
>



More information about the Standards mailing list