WebDAV provider tests: how about interacting with a server?
chris.sherlock79 at gmail.com
Thu Jan 28 17:13:03 PST 2016
> On 29 Jan 2016, at 3:29 AM, Markus Mohrhard <markus.mohrhard at googlemail.com> wrote:
> Hey Giuseppe,
> On Thu, Jan 28, 2016 at 4:59 PM, Giuseppe Castagno <giuseppe.castagno at acca-esse.eu <mailto:giuseppe.castagno at acca-esse.eu>> wrote:
> Hi Chris,
> On 01/28/2016 02:15 AM, Chris Sherlock wrote:
> This is pretty cool :-)
> I’ve currently got an odd issue with Calc not detecting the content-encoding via the WebDAV layer in bug 95217 - https://bugs.documentfoundation.org/show_bug.cgi?id=95217 <https://bugs.documentfoundation.org/show_bug.cgi?id=95217> - Persian test in a webpage encoded as UTF-8 is corrupting.
> Is it worthwhile having an optional component that runs a local webserver that can test out stuff like this?
> I was thinking about having VM, each of one with it's own server,eg. Apache WebDAV, Alfresco, Windows 7 Profession WebDAV, eXo Platform
> I don't know if this can be obtained adding an optional component.
> So the ideal solution would be to stub the external dependency and avoid the need for an external service. IMHO it is the only way how such a test can be written and be included into the normal LibreOffice build. All other solutions require that this will be only run in some special circumstances (which means in the end never). You can have a look at how Cedric solved that problem for libcmis if you need some inspiration.
> If you need help or need more information how to stub a dependency please contact me.
Yeah, agreed - probably a set of mock tests might be worthwhile.
I’m going to keep working on the font stuff, but will try to revisit this soon. Thanks Markus.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the LibreOffice