Framework for Running Test Suites on Software Tools
DejaGnu is a framework for testing other programs. Its purpose is to
provide a single front-end for all tests. Beyond this, DejaGnu offers
several advantages for testing:
1. The flexibility and consistency of the DejaGnu framework make it
easy to write tests for any program.
1. DejaGnu provides a layer of abstraction that allows you to write
tests that are portable to any host or target where a program
must be tested. For instance, a test for GDB can run (from any
Unix-based host) on any target architecture that DejaGnu
supports.
1. All tests have the same output format. This makes it easy to
integrate testing into other software development processes.
DejaGnu's output is designed to be parsed by other filtering
scripts and it is also human-readable.
DejaGnu is written in expect, which in turn uses "Tcl"--Tool command
language.
Running tests requires two things: the testing framework and the test
suites themselves.
- Sources inherited from project SUSE:SLE-12-SP3:GA
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout SUSE:SLE-12-SP3:Update/dejagnu && cd $_
- Create Badge
Source Files
Filename | Size | Changed |
---|---|---|
dejagnu-1.6.tar.gz | 0000523969 512 KB | |
dejagnu-1.6.tar.gz.sig | 0000000543 543 Bytes | |
dejagnu.changes | 0000010365 10.1 KB | |
dejagnu.keyring | 0000005407 5.28 KB | |
dejagnu.spec | 0000003242 3.17 KB | |
site.exp | 0000000723 723 Bytes |
Latest Revision
cf. fate#323428 (just you can stage it early) - Update to 1.6 * Proper support for target communication via SSH has been added. * A large number of very old config and baseboard files have been removed. If you need to resurrect these, you can get them from version 1.5.3. If you can show that a board is still in use, it can be put back in the distribution. * The --status command line option is now the default. This means that any error in the testsuite Tcl scripts will cause runtest to abort with exit status code 2. The --status option has been removed from the documentation, but will continue to be accepted for backward compatibility. * runtest now exits with exit code 0 if the testsuite "passed", 1 if something unexpected happened (eg, FAIL, XPASS or UNRESOLVED), and 2 if an exception is raised by the Tcl interpreter. * runtest now exits with the standard exit codes of programs that are terminated by the SIGINT, SIGTERM and SIGQUIT signals. * The user-visible utility procedures `absolute', `psource' and `slay' have been removed. If a testsuite uses any of these procedures, a copy of the procedure should be made and placed in the lib directory of the testsuite. * Support was added for testing the D compiler. * ~/.dejagnurc is now loaded last, not first. This allows the user to have the ability to override anything in their environment (even the site.exp file specified by $DEJAGNU). * The user-visible utility procedure `unsetenv' is deprecated and will be removed in the next release. If a testsuite uses any of these procedures, a copy of the procedure should be made and placed in the lib directory of the testsuite. - Run tests during build
Comments 0