Re: Unit testing and roguelikes

On 2003-12-02, The Sheep <[EMAIL PROTECTED]> wrote:
> Dnia Tue, 02 Dec 2003 12:00:10 +0100, Hansjörg Malthaner napisal(a):
> Seems strange to me. The modules you can easily test using such an automated
> method are simple -- both to write and debug.  On the other hand, creating
> a testing module for more complicated modules seems to be even more
> complicated...
>
> For example, how to automatically test FOV routine? Or item manipulating
> (pick up, drop, put into bag, use, wield, take off, etc.) routines?

Compare results you know that are what you want with what you get. This
is the general idea of unit testing. The reasoning behind the tests is
that if you remove the bugs in the low level, there will be less bugs as
you move up.

> How to tell automatically whether a level generator works properly?

Depends on how you define a good level :)

> Also, how to automatize testing of keyboard input and/or monitor output,
> without specialized external hardware to tap the keys and observe the screen?

Google expect.

-- 
{ Marek Baczyński :: UIN 57114871 :: GG 161671 :: JID [EMAIL PROTECTED]  }
{ http://www.vlo.ids.gda.pl/ | imbaczek at poczta fm | http://www.promode.org }
.. .. .. .. ... ... ...... evolve or face extinction ...... ... ... .. .. .. ..