Re: [fuse-devel] File-System unit-tests

[Sven U. <utc...@in...>]

Hello all,

for the time being I've managed to work around the bug in getconf.
But here comes the next question:

The typical test-cycle is:
- create a file/directory
- do something with the file/directory
- delete the file/directory

However, my filesystem is in essence meant to be RO, and therefore
lacks mknod() (as well as some other calls).  So what do you think
would be the best way to adapt the tests to my FS:

1) emulate mknod() --- I could do that by directly executing the
   corresponding SQL-statements.
2) work on a fixed set of pre-created files/directories --- I could
   populate a directory .../test/ with all the needed files.

1) has the disadvantage that it would test some functionality which
really doesn't exist, while 2) would make it difficult to start from a
clean slate...

Any ideas?

Sven
-- 
  __ _  _ __  __ __ 
 / _` || '  \ \ \ /
 \__, ||_|_|_|/_\_\  http://kogs-www.informatik.uni-hamburg.de/~utcke/Private/
 |___/     Key fingerprint =  6F F8 55 1C F9 E3 A8 F7  09 DF F7 2C 25 0C 54 53