From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19614 invoked by alias); 27 Oct 2003 14:53:03 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 19607 invoked from network); 27 Oct 2003 14:53:02 -0000 Received: from unknown (HELO mta3.adelphia.net) (68.168.78.181) by sources.redhat.com with SMTP; 27 Oct 2003 14:53:02 -0000 Received: from sbnhxyqkh6 ([68.169.251.17]) by mta3.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031027145304.YIDG6440.mta3.adelphia.net@sbnhxyqkh6>; Mon, 27 Oct 2003 09:53:04 -0500 From: "Erik Jessen" To: "'Jim Kingdon'" , Cc: Subject: RE: Test Cases (was RE: Compound Terrain Effects) Date: Mon, 27 Oct 2003 16:28:00 -0000 Message-ID: <000201c39c9b$109a08a0$6401a8c0@sbnhxyqkh6> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <200310270457.h9R4vOr22999@panix5.panix.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003/txt/msg00530.txt.bz2 Could you tell me how to check that something happened in the Make file? I don't know how to run a game for a couple of turns, save it, then check for things inside the saved game. Erik -----Original Message----- From: Jim Kingdon [mailto:kingdon@panix.com] Sent: Sunday, October 26, 2003 8:57 PM To: mcdonald@phy.cmich.edu Cc: ejessen@adelphia.net; xconq7@sources.redhat.com Subject: Re: Test Cases (was RE: Compound Terrain Effects) > Thanks for taking the time to do this. Not only can they be > instructional to others . . . Yeah. Demonstrating each feature with a 10-20 hex, 1-2 unit example is really good in a lot of ways. > but can serve as test cases to make sure features still work after > changes to the Xconq kernel. This would be maximally useful if you can run "make check" and get a pass/fail type result. Right now there are only one or two tests that work like that (see check-auto in test/Makefile.in and autotest in kernel/skelconq.c and autotest.c). But if that is too hard (as in, "the perfect is the enemy of the good" or "let's check it in while we work on it" or whatever), then an explanation of how to manually see whether the examples are working right would be helpful. > I am not quite sure where to put them. There are a number of such things in the test directory. Although those go with the current tests (which are mostly semi-automated) rather than primarily being aimed at human consumption. So I'd probably say put them in test, although I could also see a new directory examples or test/examples if there is no intention of writing test code to use them.