[QGIS-Developer] What to do about WFS test failures?

[Régis Haubourg]

Hi,
I just checked the goals of the work on the WFS provider. It is not a
refactor in fat, sorry for having used that word. The work consists in
having a closer look to the WFS and snapping cache interactions because
they cause lots of problems when the distant database has triggers that
would require WFS cache reloading and then snapping cache reloading.
Maybe Vincent can tell more about that, but it's not a major change then. I
should'nt have raised the hand here, sorry for the noise.
Regards,
Régis

Le mar. 4 sept. 2018 à 08:51, Jonathan Moules <jonathan-lists at lightpear.com>
a écrit :

> I'd suggest based on Tom's post that the work should include some sort of
> reliable way of testing the WFS client (and of course full test coverage) -
> I don't know if GeoServer is Docker-happy these days, but the default
> install in a VM should be sufficient for the task (it comes with test
> layers) - although GeoServer doesn't support WFS-T for writing.
> Cheers,
> Jonathan
>
> On 03/09/2018 12:04, Régis Haubourg wrote:
>
> Hi all,
> I very much think that the WFS client is an really bad state, and is not
> really reliable, especially in WFS-T context.
> The good news is that we just have been funded to refactor it !
> The work should start in september and land in 3.6. I will let our dev's
> come here with more technical details about the goals. I hope we will also
> be able to take benefit of this to this the OGC compliancy of the client
> here.
> Best regards,
> Régis
>
> Le lun. 3 sept. 2018 à 11:36, Tom Chadwin <tom.chadwin at nnpa.org.uk> a
> écrit :
>
>> I can't offer any helpful suggestions, but just to let you know I finally
>> had
>> to disable all my plugin WFS tests. I used to cope, by rerunning failed
>> Travis runs, but by about three months ago, it seemed no longer usable -
>> failure after failure.
>>
>> I was using a third-party WFS, and perhaps I could have got round this by
>> adding a WFS provider to the test docker image, but in this plugin's
>> case, I
>> didn't think it worth the significant effort to do so. The WM(T)S tests
>> also
>> use third-party sources and seem stable, so perhaps this wasn't the
>> underlying issue anyway.
>>
>> If an improvement or solution could be found, it would be great to
>> reinstate
>> these tests.
>>
>> Thanks
>>
>> Tom
>>
>>
>>
>> -----
>> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
>> --
>> Sent from:
>> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer at lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> _______________________________________________
> QGIS-Developer mailing listQGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20180904/39ccf9e5/attachment-0001.html>