On Sat, Dec 27, 2008 at 1:09 AM, Karel Zak <kzak@xxxxxxxxxx> wrote: > We already have a regression test that creates/extracts a cramfs > image (see tests/ts-cramfs-mkfs). The test is probably good enough > for the current mkfs.cramfs functionality. But (now) we also need to > test endianness support, fsck.cramfs and the -N option. Maybe you can > try to create a new (and simple) ts-cramfs-endianness test. > An easy and effective way to write these tests is to use pre-built cramfs images. This allows testing that fsck correctly detects both endian types. Since distributing binaries can be problematic, would it be OK if the tests use pre-built cramfs images? An alternative is to have the test first create an image and then see if fsck detects the expected endianness and extracts correctly. However, since both fsck and mkfs share the endianness code, it would mean testing the code using itself, which could hide potential problems. Regards, Roy Peled -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
