Hi all,
I want to code with TDD, but before i need to use that. I try the "make check" and that uses CxxTest, but the result is far from what i was waiting... See the end please (before that was only compiling outputs):
g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/python2.5 -I/usr/include/freetype2 -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DRELAYTOOL_CRYPTO='static const int libcrypto_is_present = 1; static int __attribute__((unused)) libcrypto_symbol_is_present(char *m) { return 1; }' -DRELAYTOOL_SSL='static const int libssl_is_present = 1; static int __attribute__((unused)) libssl_symbol_is_present(char *m) { return 1; }' -DHAVE_SSL -I/usr/include/libwpg-0.1 -I/usr/include/libwpd-0.8 -I/usr/include/poppler -D_REENTRANT -I/usr/include/poppler/glib -I/usr/include/poppler -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/pixman-1 -DPOTRACE="potrace" -D_REENTRANT -pthread -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairomm-1.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/pixman-1 -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/atk-1.0 -I/usr/include/libxml2 -I/usr/include/gtkspell-2.0 -I../cxxtest -Werror=format-security -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2 -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -g -O2 -fopenmp -MT libnr/test-nr.o -MD -MP -MF $depbase.Tpo -c -o libnr/test-nr.o libnr/test-nr.cpp &&\ mv -f $depbase.Tpo $depbase.Po In file included from libnr/test-nr.cpp:366: ././libnr/nr-point-fns-test.h:22: warning: floating constant exceeds range of 'double' In file included from libnr/test-nr.cpp:428: ././libnr/in-svg-plane-test.h:18: warning: floating constant exceeds range of 'double' In file included from libnr/test-nr.cpp:13: ././libnr/nr-compose-test.h:33: error: explicit template specialization cannot have a storage class make[2]: ** [libnr/test-nr.o] Erro 1 make[2]: Saindo do diretório `/opt/inkscape-svn/src' make[1]: ** [check-am] Erro 2 make[1]: Saindo do diretório `/opt/inkscape-svn/src' make: ** [check-recursive] Erro 1
There is no testing dots with Fails and Errors marks. There is only a compilation error trowing. :-(
What is wrong? The unity testing infrastructure is really working?
Aurium
Aurélio A. Heckert wrote:
... There is no testing dots with Fails and Errors marks. There is only a compilation error trowing. :-(
What is wrong? The unity testing infrastructure is really working?
It used to :) Over the summer I worked on getting it into shape, and recently it still worked for me on Windows, but I currently can't test it on Linux myself. If you can be of any help in getting it working again that would be great (if it also fails on Windows I'll probably get around to having a look on Tuesday).
On Thu, Nov 27, 2008 at 5:22 PM, Jasper van de Gronde <th.v.d.gronde@...528...> wrote:
Aurélio A. Heckert wrote:
... There is no testing dots with Fails and Errors marks. There is only a compilation error trowing. :-(
What is wrong? The unity testing infrastructure is really working?
It used to :) Over the summer I worked on getting it into shape, and recently it still worked for me on Windows, but I currently can't test it on Linux myself. If you can be of any help in getting it working again that would be great (if it also fails on Windows I'll probably get around to having a look on Tuesday).
Ooh... I'm not the right guy to do that. :-/ But i believe in TDD and i think is important to make that back to work. Someone may do it?
We may use a commit role: Comity only after the "make check" Ok! I and my friends use this role where i work, and is interesting to see how we do bad interactions with other unexpected peaces of code.
Aurium
Aurélio A. Heckert wrote:
On Thu, Nov 27, 2008 at 5:22 PM, Jasper van de Gronde <th.v.d.gronde@...528...> wrote:
Aurélio A. Heckert wrote:
... There is no testing dots with Fails and Errors marks. There is only a compilation error trowing. :-(
What is wrong? The unity testing infrastructure is really working?
It used to :) Over the summer I worked on getting it into shape, and recently it still worked for me on Windows, but I currently can't test it on Linux myself. If you can be of any help in getting it working again that would be great (if it also fails on Windows I'll probably get around to having a look on Tuesday).
Ooh... I'm not the right guy to do that. :-/ But i believe in TDD and i think is important to make that back to work. Someone may do it?
I just tried simply compiling and running it on Windows and had no problems whatsoever (with latest SVN). (No problems means that the tests compile and run, not that they all succeed, actually quite a few fail.) What version of GCC are you using?
We may use a commit role: Comity only after the "make check" Ok! I and my friends use this role where i work, and is interesting to see how we do bad interactions with other unexpected peaces of code.
There is definitely something to be said for such schemes, but I don't think that in the context of Inkscape this is a realistic scenario. If all the tests would be successful to begin with it might be possible to enforce something like this using technical measures, but even then it is doubtful if it would be beneficial.
What I would like to do is raise "public" awareness of these tests, for example by letting the tests run periodically and generating automatic notifications if something suddenly fails (or succeeds!) that could be sent to the developer mailinglist or something like that. If you're interested in helping out with things like this or have some ideas of your own, you're more than welcome to help out!
participants (2)
-
Aurélio A. Heckert -
Jasper van de Gronde