FreeLists / openbeosstorage / [openbeosstorage] Re: BResources

[Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>]

On Thu, 2 May 2002, Tyler Dauwalder wrote:

> > Regarding the test suite for BResources, it may be a good idea to provide
> > some resource files for the tests. Otherwise it can only be ensured that
> > our BResources can eat the stuff, it created, but leaves open, if it is
> > compatible with the original Be resources.
> > Where would I put those files? In a subdirectory in test/ ?
> > Mmh, I just have the idea, that I could write a little command to create
> > and edit resource files. Then the test files could be created on the
> > fly. Excutables had to be at tested as well... but we have /bin...
> > Mmh, I will think about it.
> 
> Yeah, I would go with the second method. You could use mwdres to dump a 
> resource file from something in /boot/beos/apps too. 

I finally decided rather to add test files (in test/resources).
It's just not sure, that the files I would have chosen would be identical
on all installations the tests might run on; future ones (e.g. OBOS R1
alpha) in particular. Now I have a set of files of four different flavors
(ELF, PEF, x86 and PPC resource files) with well-defined resources. That
made writing the tests easier.

CU, Ingo

PS: I added the targets `r5' and `posix' to test/Jamfile. These are quite
    handy when writing tests -- then you usually want to compile only the
    R5 test app -- and when testing the OBOS implementation -- then one
    is merely interested on compiling the other version.

    Furthermore I added the method TestShell::TestDir() that returns the
    path of the directory the test application lives in. This was
    necessary to locate the new test files.