Re: WebDAV provider tests: how about interacting with a server?

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 - Persian test in a webpage encoded as

Re: WebDAV provider tests: how about interacting with a server?

> I was thinking about having VM, each of one with it's own server,eg. Apache > WebDAV, Alfresco, Windows 7 Profession WebDAV, eXo Platform Using a vm, would mean it would a special test, which would not be part of standard testing. Is it not possible to make a set of test, that can be

Re: WebDAV provider tests: how about interacting with a server?

Hey Giuseppe, On Thu, Jan 28, 2016 at 4:59 PM, Giuseppe Castagno < giuseppe.casta...@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

Re: WebDAV provider tests: how about interacting with a server?

> On 29 Jan 2016, at 3:29 AM, Markus Mohrhard > wrote: > > Hey Giuseppe, > > On Thu, Jan 28, 2016 at 4:59 PM, Giuseppe Castagno > > > wrote: > Hi Chris, > > On 01/28/2016 02:15 AM, Chris

Re: WebDAV provider tests: how about interacting with a server?

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 - Persian test in a webpage encoded as UTF-8 is corrupting. Is it worthwhile having an optional

WebDAV provider tests: how about interacting with a server?

Hi all, after the first very trivial test on WebDAV provider, I would like to implement the 'real' unit tests with a server. The reason is obvious: in the end is with an external server that ucp.webdav will interact. This will permit to stimulate all the three layers the provider has