manpagez: man pages & more
info dejagnu
Home | html | info | man
[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

Index: F – O

Jump to:   -   .  
A   B   C   D   E   F   G   H   I   K   L   M   N   O   P   Q   R   S   T   U   V   W   X  
Index Entry Section

F
FAIL2.4 A POSIX conforming test framework
fail "string"5.3.1 Core Internal Procedures
failing test, expected3. Using runtest
failing test, known3. Using runtest
failing test, unexpected3. Using runtest
failure, conditional expected5.3.1 Core Internal Procedures
failure, expected5.3.1 Core Internal Procedures
failure, known5.3.1 Core Internal Procedures
failure, POSIX definition2.4 A POSIX conforming test framework
filename for test files5.1 Conventions for using tool names
files matching a pattern5.3.3 Utility Procedures
find dir pattern5.3.3 Utility Procedures
findfile5.2 Initialization module
finding file differences5.3.3 Utility Procedures
future directions2.5 Future directions

G
gdb.t00/echo.exp2.2 What does a DejaGnu test look like?
getdirs dir5.3.3 Utility Procedures
getdirs dir pattern5.3.3 Utility Procedures
getenv var5.3.3 Utility Procedures
getting environment variables5.3.3 Utility Procedures
get_warning_threshold5.3.1 Core Internal Procedures
GNATS bug number6.5 Special variables used by test cases
Granlund, Torbjorn6.1 Writing a test case
grep filename regexp5.3.3 Utility Procedures
grep filename regexp line5.3.3 Utility Procedures

H
help with runtest3. Using runtest
hints on test case writing6.4 Hints on writing a test case
host config name, changing3. Using runtest
host configuration test5.3.1 Core Internal Procedures
host, explainedA. Installing DejaGnu
host_triplet4.0.1 Config Variables

I
ignoretests4.0.1 Config Variables
init file name5.2 Initialization module
init file, purpose5.2 Initialization module
initialization5.2 Initialization module
input files5.6 The files DejaGnu reads
installed tool name5.3.1 Core Internal Procedures
installing DejaGnuA.2 Installing DejaGnu
internal details5. The DejaGnu Implementation
invoking3. Using runtest
IP network procedures5.3.2 Remote Communication Procedures
isbuild "host"5.3.1 Core Internal Procedures
ishost "host"5.3.1 Core Internal Procedures
isnative5.3.1 Core Internal Procedures
istarget "target"5.3.1 Core Internal Procedures

K
kermit port bps5.3.2 Remote Communication Procedures
kermit, remote testing via3. Using runtest
KFAIL2.4 A POSIX conforming test framework
KFAIL, avoiding for POSIX2.4 A POSIX conforming test framework
KFAIL, producing5.3.1 Core Internal Procedures
known failure3. Using runtest
known failure5.3.1 Core Internal Procedures
known failure, cancelling5.3.1 Core Internal Procedures
KPASS2.4 A POSIX conforming test framework
KPASS, producing5.3.1 Core Internal Procedures

L
last command output6.5 Special variables used by test cases
lib/debugger.exp5.3.5 Debugging Procedures
lib/remote.exp5.3.2 Remote Communication Procedures
lib/target.exp5.3.4 Cross target procedure
lib/utils.exp5.3.3 Utility Procedures
Libes, Don2.6 Tcl and Expect
list, pruning5.3.3 Utility Procedures
lists supported targets5.3.4 Cross target procedure
list_targets5.3.4 Cross target procedure
load library file5.3.1 Core Internal Procedures
load procedure, tested tools5.4 Target dependent procedures
load_lib "library-file"5.3.1 Core Internal Procedures
local ‘site.exp4.0.3 Local Config File
log files, where to write3. Using runtest
Lupton, Robert7.1 Writing tests for a new tool

M
make builds part of testsA.1 Configuring the DejaGnu test driver
make check2.1 Running existing tests
master ‘site.exp4.0.2 Master Config File
Menapace, Julia2.3 Design goals
mondfe5.5 Remote targets supported
mondfe, remote testing via3. Using runtest

N
name “DejaGnu”2.3 Design goals
name for remote test machine3. Using runtest
name transformations5.3.1 Core Internal Procedures
name, initialization module5.2 Initialization module
naming conventions5.1 Conventions for using tool names
naming tests to run3. Using runtest
naming tests to run3. Using runtest
native configuration2.1 Running existing tests
native configuration test5.3.1 Core Internal Procedures
network (IP) procedures5.3.2 Remote Communication Procedures
NOTE3. Using runtest
NOTE5.3.1 Core Internal Procedures
note "string"5.3.1 Core Internal Procedures

O
objdir4.0.1 Config Variables
object directory3. Using runtest
Opening a remote connection5.3.2 Remote Communication Procedures
operating principles5. The DejaGnu Implementation
option defaults4.0.1 Config Variables
option list, runtest3. Using runtest
options3. Using runtest
options for runtest, common2.1 Running existing tests
options, Tcl variables for defaults4.0.1 Config Variables
order of tests5.1 Conventions for using tool names
Ousterhout, John K.2.6 Tcl and Expect
outdir4.0.1 Config Variables
output directory3. Using runtest
output files5.7 The files DejaGnu writes
output, additional3. Using runtest
overriding ‘site.exp4. Setting runtest defaults
overview1. What is DejaGnu?

Jump to:   -   .  
A   B   C   D   E   F   G   H   I   K   L   M   N   O   P   Q   R   S   T   U   V   W   X  

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]
© manpagez.com 2000-2017
Individual documents may contain additional copyright information.