Site setup & terminology

[Gary Cote]

A few years back, I worked at a place that used dejagnu
pretty extensively. I didn't set up the environment;
just added my own little test cases and such. Now, I'm
trying to spread the dejagnu gospel to my current company.

So ... I'm trying to establish a functional, but not overly
elaborate, dejagnu environment. And I'm having a bit of a
hard time bootstrapping myself, so to speak. I'm finding
the terminology sprinkled throughout the user manual, man
page, and info pages particularly confusing. 

Can someone please elaborate on what each of the following
would be? Some nice, concrete examples would be nice too.
I can't tell whether they refer to specific machines (real, 
physical hosts that i can logon to), types of machine 
(say a linux pc or an SBC running VxWorks), or the role
the machine is playing (executing testcases, system under
test), etc etc.

Target & Board
. What the heck is the difference between target & board? 
. Is target the type of board you're using and it's 
characteristics in general (os, compiler, linker, init procs)? 
. And is board the site-specific configuration (node names, 
addresses, software revs, usernames, passwords)?
                  
Tool
. Is this the program you're testing, or the program you're 
executing to perform the tests?

Host
. Runtest manpage has a -host and -name option. What's the diff? 
Is host the node running dejagnu?


My setup is relatively simple ... I have a machine, call it scooby,
that houses my development environment, source code, tools, etc.
It will run dejagnu. It uses ssh to talk to another machine, call
that one shaggy, that is the target. It contains runtime software 
and conifguration such as one would expect in a product environment.

Thanks for a great tool. And thanks in advance for helping me
spread the word to the masses :)