Note: This web site is only kept up to date for OSG Software 1.2 (VDT 2.0.0). If you are looking for information for the most recent release, the RPM-based OSG Software 3.0, please see the OSG documentation web site

Running Tests Manually

  1. Make sure no other VDT is running One nice trick is:
    ps auwx | grep vdt | awk '{print $2}' | xargs kill
  2. Install the package(s) under test
    /opt/pacman/pacman -get
  3. Install the VDT-Test package
    /opt/pacman/pacman -get
  4. Source a setup script
  5. (Pre-2.0) Load answers to the VDT questions into your environment
  6. Perform post-installation setup; do one of:
    • Use the script.
      • If you are working on the 2.0 or higher branches, it is versioned and you can find it in
      • If you are working on an older branch, you need to download the script:
        curl -O
        chmod 0755
    • Go through the post-install/README file and follow instructions in it, as necessary
  7. Check standard out, vdt-install.log, and currently running processes to make sure everything is running
  8. Run your test(s)
    cd vdt/tests/tests
    ../vdt-run-tests --verbose --user vdttest --test <test file name>
    Grid cert passphrase is 'vdttest'

Imitating tests as run nightly

  1. Become root
  2. Kill off all VDT processes:
    ps auwx | grep vdt | awk '{print $2}' | xargs kill
  3. Run an at job. Try the first for all tests, the second for just the VDT:
    > at now + 1 minute
    at> /vdt/bin/vdt-run-install-tests -d
    at> (type control-d)
    > at now + 1 minute
    at> /vdt/bin/vdt-run-install-tests --package VDT --version 1.10.1
    at> (type control-d)
  4. If you have a test cache, put it in place of the version in the version specifier. For example, if your test cache is /p/vdt/public/html/test-cache/matyas use
    > at now + 1 minute
    at> /vdt/bin/vdt-run-install-tests --package VDT --version test-matyas
    at> (type control-d)
  5. For more information on test caches, see this page