Hi Michael,
On Fri, 2010-12-03 at 11:57 +, Michael Meeks wrote:
> It failed after only a handful of documents on the attached with:
>
> #0 0xabd83b95 in
> writerfilter::dmapper::DomainMapper_Impl::finishParagraph(boost::shared_ptr)
> ()
>from /data/opt/OOInstall/program/../basis-
On Fri, 2010-12-03 at 11:57 +, Michael Meeks wrote:
> closing them all in a big long churning run every now and then would
> catch a ton of bugs for us :-)
>
> Any volunteers to play with it ?
Hmm; perhaps this is just all .docx stuff since these are the first
files in the test suite
On Fri, 2010-11-19 at 16:03 +, Caolán McNamara wrote:
> On Fri, 2010-11-19 at 01:32 +0100, Miklos Vajna wrote:
> > I'm asking because I guess the more complex to run it, the fewer people
> > will actually try it out at all.
>
> True. I was sort of wondering about potential colossal size. But
On Fri, 2010-11-19 at 01:32 +0100, Miklos Vajna wrote:
> Is 3) about cppunit as well? If yes, what about just having 3) in the
> tree as well, and then it could be invoked with a 'make check' or
> similar that would run all those tests.
>
> I'm asking because I guess the more complex to run it, th
On Thu, Nov 18, 2010 at 11:58:29AM +, Caolán McNamara
wrote:
> 1) basic cppunit tests take place during the build, keep us honest and
> basic functionality working at all times. Have a few of these at the
> moment.
> 2) smoketest run at the end of the build, at least by the buildbots to
> mak
On Thu, 2010-11-18 at 12:16 +0100, Gioele Barabucci wrote:
> Hello,
>
> in order to report a subtle bug [1], I had to create a minimal failing
> test case document.
>
> Is there a way to contribute this kind of testcases, and assertions on
> which results one should expect, to a testsuite so th
Hello,
in order to report a subtle bug [1], I had to create a minimal failing
test case document.
Is there a way to contribute this kind of testcases, and assertions on
which results one should expect, to a testsuite so that future changes
to the LibreOffice code can be tested against these
