Hi, Ethan, Evan and Tim I finished the wrapper which is able to make the execution much more simpler, and here is the work space of my test suite. Please try to run it and tell me your comments or ideas.
/net/rainday.prc/export/Projects/indiana/General/ws-snv-itc/src/suites/libbe. You can run the test suite by following steps: 1. Run the test suite as "root" user # su - root 2. Add the cc compiler into PATH # export PATH=$PATH:/cc/compiler/path 3. Add SUNWhea package. I have wrapped the SUNWhea package within the test suite which will be set up automatically, but because the different build has different SUNWhea packages, it will be more safety that the user could set up the package by himself. # pkgadd -d /path SUNWhea 4. Copy the test suite # cp -rf /net/rainday.prc/export/Projects/indiana/General/ws-snv-itc/src/suites/libbe /your/working/path 5. Run it. # /your/working/path/libbe/runner [ -p <free disk/partition for new zpool>] E.g.: # /your/working/path/libbe/runner Or # /your/working/path/libbe/runner -p c0t1d0 6. Check the journal - check /tmp/libbe_runner_journal.txt, and the file will tell you the real executed journal path which should be in /var/tmp/result.XXX directory. Sorry I don't write the commands above into README, because I think when I try to putback these scripts, I may not putback the runner and some other related stuffs(packages, files) into STC or ITC gate. <NOTE: the test suite is not ready yet, and the development is still ongoing. Current whole framework is fixed, and I am working on it to add more cases and make it much stronger. So I might putback some scripts at any time. Hope the putback of new scripts will not impact its stability.> Thanks Jason
