Hello, Dr.. You wrote 16 июля 2010 г., 17:37:25: >> So if spkg-check is executed, I can be sure that spkg was successfully >> installed into system? > Not exactly, as some packages unfortunately ignore errors, so if the package > fails to install, you will not know it.
I am talking about my own package, so I know that its author at least tried to handle all errors during install :) > Not all packages have spkg-check files - in fact, the majority do > not. A list of the packages which have them missing can be found on > this ticket. http://trac.sagemath.org/sage_trac/ticket/9281 Looks like that spkg-check is not very popular way of testing packages. Many packages rely on doctests. It leads me to the next question. I work on test suite for ALGLIB spkg. Previous release contained only computational core tests, now I want to add Python-C integration tests. These tests will be integrated into spkg-check. So testing will be done as follows: 1) spkg-check is called 2) computational core (external shared library) is tested 3) if failed, testing is stopped 4) communication between core and Python is tested Step (4) is just execution of very large Python script which tries to call different ALGLIB functions and to check their result. This script is automatically generated from formal description - it will allow me to use these tests later in other programming languages. It is also possible to automatically generate doctests from formal description used to generate spkg-check. So I have three options: a) to test ALGLIB from spkg-check only b) to generate doctests and to test ALGLIB using doctests only c) to use BOTH spkg-check and doctests But what should I choose in this situation? -- With best regards, Sergey mailto:sergey.bochka...@alglib.net -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
