Hi guys,
On Wed, 2006-11-08 at 11:27 +0100, Kay Ramme wrote:
> > yes, definitely. What about a staged approach to that: first include
> > all unit tests in a regular build, but _only_ perform them with a
> > magic env var set (like the debug=true stanza)?
>
> good idea, that would at least make it obvious how to trigger the tests ...
Right, knowing how to run these tests (and that they exist) is at least
a large part of the problem. Of course, if more people run them then we
get more tests, and the tests don't tend to bit-rot so quickly.
I looked at the nice list of tests on the architecture page, dived
straight into one:
http://wiki.services.openoffice.org/wiki/Uno/Cpp/Module/CPPUhelper/test
I tried the 1st test, since the instruction list for the 2nd set of
tests looked long & scary ;-) [ and presumably would be better expressed
as a simple 'check:' dmake rule instead of a hand-typed recipe ].
The result:
$ cd cppuhelper/qa/propertysetmixin/
$ dmake
... snip a surprising amount of successful building ...
g++ -fmessage-length=0 -c -Os -fno-strict-aliasing ... -o
test_propertysetmixin.o
/opt/OpenOffice/src680-m187/cppuhelper/qa/propertysetmixin/test_propertysetmixin.cxx
/opt/OpenOffice/src680-m187/solver/680/unxlngi6.pro/inc/cppunit/TestAssert.h:
In static member function ‘static _STL::string
CppUnit::assertion_traits<T>::toString(const T&) [with T = rtl::OUString]’:
/opt/OpenOffice/src680-m187/solver/680/unxlngi6.pro/inc/cppunit/TestAssert.h:100:
instantiated from ‘void CppUnit::TestAssert::assertEquals(const T&, const
T&, CppUnit::SourceLine, const _STL::string&) [with T = rtl::OUString]’
/opt/OpenOffice/src680-m187/cppuhelper/qa/propertysetmixin/test_propertysetmixin.cxx:407:
instantiated from here
/opt/OpenOffice/src680-m187/solver/680/unxlngi6.pro/inc/cppunit/TestAssert.h:50:
error: ambiguous overload for ‘operator<<’ in ‘ost << x’
/opt/OpenOffice/src680-m187/solver/680/unxlngi6.pro/inc/stl/stl/_ostream.h:96:
note: candidates are: _STL::basic_ostream<_CharT, _Traits>&
_STL::basic_ostream<_CharT, _Traits>::operator<<(unsigned char) [with _CharT =
char, _Traits = _STL::char_traits<char>] <near match>
...
Of course, it's possible that my environment is just twisted up in some
strange way of my own construction ;-) however the install from this
build works I believe so ...
Naturally it's unfair to infer that the unit tests are all broken &
under-used on the basis of the 1st one tried ;-) but ... having a
standard way to run all included unit tests [ eg. at the end of a
BuildBot build ] would be really rather useful.
Thanks,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
