• QUICK LINKS
  • answers.stanford.edu
  • apple.stanford.edu
  • computing.stanford.edu
  • courses.stanford.edu
  • datarates.stanford.edu
  • dell.stanford.edu
  • departmentphone.stanford.edu
  • email.stanford.edu
  • ess.stanford.edu
  • helpsu.stanford.edu
  • myitserviceshelp.stanford.edu
  • orderithelp.stanford.edu
  • software.stanford.edu
  • studentphone.stanford.edu
  • techtraining.stanford.edu
  • tools.stanford.edu
  • unixcomputing.stanford.edu
  • vpn.stanford.edu
  • web.stanford.edu
  • windows.stanford.edu
• SERVICES
  • IT Services Only
  • All Campus Providers
    → computing.stanford.edu
• GETTING HELP
  • Stanford Answers
  • HelpSU: IT Help Desk
  • Training
• PROJECTS
• ABOUT US
  • What We Do
  • Organization Chart
  • Strategic Plan
  • Jobs
  • Contact info
  • Service & System Metrics
• INTERNAL
• SEARCH

  • Search IT Services:
     

• Pubsw Software
• Index of Leland Software
• DejaGnu 1.4.1

DejaGnu 1.4.1

Summary

Description: Test suite framework
Source: http://www.gnu.org/software/dejagnu/

Support

This package is available for all platforms. This package is unsupported and provided on an as-is basis.

Description

DejaGnu is a framework for testing other programs. Its purpose is to provide a single front end for all tests. Think of it as a custom library of Tcl procedures crafted to support writing a test harness. A Test Harness is the testing infrastructure that is created to support a specific program or tool. Each program can have multiple testsuites, all supported by a single test harness. DejaGnu is written in Expect, which in turn uses Tcl -- Tool command language.

This description was taken from the DejaGnu web pages.

Files

   Programs: runtest
   Includes: dejagnu.h
Other Files: /usr/pubsw/lib/dejagnu
  Man Pages: runtest(1)

Accuracy

This information reflects the version of this package that is installed in Stanford's site-wide pubsw software tree. Newer versions of the package may be available from the package source. The contents of this page, including the source URL if applicable, are generally only reviewed when the package is upgraded and therefore may not accurately reflect the current version of the package.