| Index Entry | Section |
|---|
|
| F | | |
|---|
| FAIL | 2.4 A POSIX conforming test framework |
| fail "string" | 5.3.1 Core Internal Procedures |
| failing test, expected | 3. Using runtest |
| failing test, known | 3. Using runtest |
| failing test, unexpected | 3. Using runtest |
| failure, conditional expected | 5.3.1 Core Internal Procedures |
| failure, expected | 5.3.1 Core Internal Procedures |
| failure, known | 5.3.1 Core Internal Procedures |
| failure, POSIX definition | 2.4 A POSIX conforming test framework |
| filename for test files | 5.1 Conventions for using tool names |
| files matching a pattern | 5.3.3 Utility Procedures |
| find dir pattern | 5.3.3 Utility Procedures |
| findfile | 5.2 Initialization module |
| finding file differences | 5.3.3 Utility Procedures |
| future directions | 2.5 Future directions |
|
| G | | |
|---|
| gdb.t00/echo.exp | 2.2 What does a DejaGnu test look like? |
| getdirs dir | 5.3.3 Utility Procedures |
| getdirs dir pattern | 5.3.3 Utility Procedures |
| getenv var | 5.3.3 Utility Procedures |
| getting environment variables | 5.3.3 Utility Procedures |
| get_warning_threshold | 5.3.1 Core Internal Procedures |
| GNATS bug number | 6.5 Special variables used by test cases |
| Granlund, Torbjorn | 6.1 Writing a test case |
| grep filename regexp | 5.3.3 Utility Procedures |
| grep filename regexp line | 5.3.3 Utility Procedures |
|
| H | | |
|---|
| help with runtest | 3. Using runtest |
| hints on test case writing | 6.4 Hints on writing a test case |
| host config name, changing | 3. Using runtest |
| host configuration test | 5.3.1 Core Internal Procedures |
| host, explained | A. Installing DejaGnu |
| host_triplet | 4.0.1 Config Variables |
|
| I | | |
|---|
| ignoretests | 4.0.1 Config Variables |
| init file name | 5.2 Initialization module |
| init file, purpose | 5.2 Initialization module |
| initialization | 5.2 Initialization module |
| input files | 5.6 The files DejaGnu reads |
| installed tool name | 5.3.1 Core Internal Procedures |
| installing DejaGnu | A.2 Installing DejaGnu |
| internal details | 5. The DejaGnu Implementation |
| invoking | 3. Using runtest |
| IP network procedures | 5.3.2 Remote Communication Procedures |
| isbuild "host" | 5.3.1 Core Internal Procedures |
| ishost "host" | 5.3.1 Core Internal Procedures |
| isnative | 5.3.1 Core Internal Procedures |
| istarget "target" | 5.3.1 Core Internal Procedures |
|
| K | | |
|---|
| kermit port bps | 5.3.2 Remote Communication Procedures |
| kermit, remote testing via | 3. Using runtest |
| KFAIL | 2.4 A POSIX conforming test framework |
| KFAIL, avoiding for POSIX | 2.4 A POSIX conforming test framework |
| KFAIL, producing | 5.3.1 Core Internal Procedures |
| known failure | 3. Using runtest |
| known failure | 5.3.1 Core Internal Procedures |
| known failure, cancelling | 5.3.1 Core Internal Procedures |
| KPASS | 2.4 A POSIX conforming test framework |
| KPASS, producing | 5.3.1 Core Internal Procedures |
|
| L | | |
|---|
| last command output | 6.5 Special variables used by test cases |
| lib/debugger.exp | 5.3.5 Debugging Procedures |
| lib/remote.exp | 5.3.2 Remote Communication Procedures |
| lib/target.exp | 5.3.4 Cross target procedure |
| lib/utils.exp | 5.3.3 Utility Procedures |
| Libes, Don | 2.6 Tcl and Expect |
| list, pruning | 5.3.3 Utility Procedures |
| lists supported targets | 5.3.4 Cross target procedure |
| list_targets | 5.3.4 Cross target procedure |
| load library file | 5.3.1 Core Internal Procedures |
| load procedure, tested tools | 5.4 Target dependent procedures |
| load_lib "library-file" | 5.3.1 Core Internal Procedures |
| local ‘site.exp’ | 4.0.3 Local Config File |
| log files, where to write | 3. Using runtest |
| Lupton, Robert | 7.1 Writing tests for a new tool |
|
| M | | |
|---|
| make builds part of tests | A.1 Configuring the DejaGnu test driver |
| make check | 2.1 Running existing tests |
| master ‘site.exp’ | 4.0.2 Master Config File |
| Menapace, Julia | 2.3 Design goals |
| mondfe | 5.5 Remote targets supported |
| mondfe, remote testing via | 3. Using runtest |
|
| N | | |
|---|
| name “DejaGnu” | 2.3 Design goals |
| name for remote test machine | 3. Using runtest |
| name transformations | 5.3.1 Core Internal Procedures |
| name, initialization module | 5.2 Initialization module |
| naming conventions | 5.1 Conventions for using tool names |
| naming tests to run | 3. Using runtest |
| naming tests to run | 3. Using runtest |
| native configuration | 2.1 Running existing tests |
| native configuration test | 5.3.1 Core Internal Procedures |
| network (IP) procedures | 5.3.2 Remote Communication Procedures |
| NOTE | 3. Using runtest |
| NOTE | 5.3.1 Core Internal Procedures |
| note "string" | 5.3.1 Core Internal Procedures |
|
| O | | |
|---|
| objdir | 4.0.1 Config Variables |
| object directory | 3. Using runtest |
| Opening a remote connection | 5.3.2 Remote Communication Procedures |
| operating principles | 5. The DejaGnu Implementation |
| option defaults | 4.0.1 Config Variables |
| option list, runtest | 3. Using runtest |
| options | 3. Using runtest |
| options for runtest, common | 2.1 Running existing tests |
| options, Tcl variables for defaults | 4.0.1 Config Variables |
| order of tests | 5.1 Conventions for using tool names |
| Ousterhout, John K. | 2.6 Tcl and Expect |
| outdir | 4.0.1 Config Variables |
| output directory | 3. Using runtest |
| output files | 5.7 The files DejaGnu writes |
| output, additional | 3. Using runtest |
| overriding ‘site.exp’ | 4. Setting runtest defaults |
| overview | 1. What is DejaGnu? |
|
