Hi all,
Jan Holesovsky wrote on 01-08-15 02:43:
> + !!!please file easy hacks if you have ideas!!! (Bjoern)
For ideas, query with "needsDevEval" in Whiteboard.
At least part of those could be good candidates.
Thanks,
--
Cor Nouws
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28
Hey,
On Sun, Aug 2, 2015 at 9:01 PM, Norbert Thiebaud
wrote:
> On Sun, Aug 2, 2015 at 11:25 AM, Markus Mohrhard
> wrote:
>
>
> >> AI: + will have a look at the CppUnit to implement 'expected
> failure'
> >> (Jan-Marek)
> >> + Cpp logs are e.g. in
> >> workdir/CppunitTest/sal_rtl
Hi,
On Sun, Aug 02, 2015 at 06:25:05PM +0200, Markus Mohrhard wrote:
> That is already possible with cppunit. Instead of using CPPUNIT_TEST use
> CPPUNIT_TEST_FAIL which tells cppunit that the test is expected to fail
> with a cppunit exception being thrown (it is extensively used in the
> cppunit
On Sun, Aug 2, 2015 at 11:25 AM, Markus Mohrhard
wrote:
>> AI: + will have a look at the CppUnit to implement 'expected failure'
>> (Jan-Marek)
>> + Cpp logs are e.g. in
>> workdir/CppunitTest/sal_rtl_math.test.log
>
>
>
> That is already possible with cppunit. Instead of using C
>
> * Areas that require unit tests with each bugfix (Markus/???)
> + https://wiki.documentfoundation.org/Development/Unit_Tests
> + updated the page with the areas where tests for fixes are
> mandatory (Kendy)
> + so far: chart2, writer filters (import + export)
> + do
