Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 2 Oct 2001 15:32:16 +0400 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <1399887427.20011002153216@logos-m.ru> To: Christopher Faylor Subject: Re: The test suite is cool In-Reply-To: <20011001194848.A30610@redhat.com> References: <20011001194848 DOT A30610 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Tuesday, 02 October, 2001 Christopher Faylor cgf AT redhat DOT com wrote: CF> I just wanted to spread some test suite kudos in Egor's direction. well, most kudos should go to the guys from linux testing project, i just did the porting. CF> I've been trying to school myself to run the test suite before I check in CF> changes and whaddaya know? I've found some problems in my code (I can CF> hear the collective gasps now). cool indeed :) i wonder if it's possible to add 'make check' to snapshot building scripts (if they're running natively, of course) and post results on snapshots page. CF> I'd like to start adding some more regression tests to the testsuite. I CF> know that I could figure out how to do this but I'm wondering if a CF> "how-to-add-things-to-the-test-suite" would be appropriate. CF> Egor, would you be willing to add something like this? hmm, i don't really know what can i add to README written by DJ. Maybe except CYGWIN_TESTSUITE_TESTS variable description, which is rather recent addition. for those who interested, this variable can be used to make testsuite skip all tests except those that match regexp, assigned to this variable. so, if i want to run e.g. lseek tests only, i start testsuite with something like 'make check CYGWIN_TESTSUITE_TESTS=\.\*lseek\.\*' otherwise, one should just write a *.c program which returns 0 status on success and non-zero on failure. what i definitely _can_ write is a testsuite TODO :) i have some ideas to make testsuite more useful (this includes [better] w9x support, testing for memory leaks, some kind of benchmarking etc.) Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19