Hi Tim, Thanks a lot for your response! I'll make sure the info about the GNet status makes it to my project manager. I hope there's a good reason why they decided to integrate this library into JDS. Perhaps there are some apps on the integration list which depending on it. I installed the dependencies on my laptop and I'm now able to run the check based tests. I have to forget about the Valgrind ones though. They do not support Solaris and porting would be a tremendous task due to tight dependencies on the Linux kernel. I noticed there were 11 test suites, GNetABI, GNetBase64, GConn, GConnHttp, GNetHashes, GInetAddr, GNetIPv6, GNetMisc, GNetPacking, GNetUnpacking and GURI. While some of the test names are self-explaining (like GNetHashes is likely to test SHA and MD5), others are a bit mystery for me. As there is no test documentation, I was wondering whether you could provide me very short desc on the individual check tests, like which features each of them covers? Do the check tests cover all or at least most of the major features? Testing the library using an app built on top of GNet is of course a good idea. The only question is efficiency. Such a task would require me to port the app onto Solaris (unless it has been already done, like Pan on Blastwave) which may or may not be easy. Most apps listed on your web site seem to be almost dead, with the last source code changes dated a few years back. The only exceptions are Pan, Workrave and Mail Notification icon which seem to provide a very small test coverage. For these reasons I was wondering whether I should spend my limited resources on this and I was interested in your opinion. Thanks, Robert Tim-Philipp Müller wrote: On Tue, 2008-12-23 at 19:01 +0100, Robert Pes wrote: Hi,My name is Robert Pes and I work for Sun Microsystems. I'm just about to start to work with my colleague David Fan on integration of your GNet library into Java Desktop System (JDS). I'll be responsible in particular for testing of the library after its integration into the JDS consolidation. The goal is to make sure that the all the library features work as expected.That's great! However, you do realise that GNet is basically in maintenance-only mode for all practical purposes, right? It will hopefully be replaced/superseded by a spiffy new network API in GLib (gnio etc.) in the not too distant future.I noticed there were some test suites attached to your source tarball. I tried to run them using "make check" but there were no visible results. Is there any trick in running them?You probably need the 'check' library installed (check.sf.net IIRC), optionally also valgrind + valgrind-headers if you want valgrind support (and your platform supports it). Same as you need to run 'make check' for GStreamer basically.I was also wondering whether there is any test documentation describing the test scope, feature coverage and expected results. I didn't find anything either in available docs or the tests/ folder and the test source code is not that easy to read (I'm rather Java programmer than C one).'make help' in $srcdir/tests/check will give you an overview of the options. 'make check' or 'make check-valgrind' in the top-level dir should be enough for most purposes. There is no further documentation than that I'm afraid. The output should look something like: Running suite(s): GTcpSocket ...........125 attempts 100%: Checks: 1, Failures: 0, Errors: 0 PASS: gnet/gnettcpsocket Running suite(s): GNetABI ...I was also thinking of running one of the applications using GNet, like e.g. Mail Notify, to verify functionality of your library. Do you think it's a good idea?How could that possibly not be a good idea? :)Which application would in your opinion provide the best coverage of the supported features?I don't think there's one application, as applications tend to use only a very limited subset of features. Cheers -Tim _______________________________________________ gnet-devel-list mailing list gnet-devel-list gnome org http://mail.gnome.org/mailman/listinfo/gnet-devel-list |