Adding A New Board

Prev<<< PreviousExtending DejaGnu

Chapter 4. Extending DejaGnu

NextNext >>>

Example 4-6. Testing a New Board Config FileExample 6. Testing a New Board Config File

, which is the Tcl execution characters.

Example 4-7. Example Board Config FileExample 7. Example Board Config File

Prev<<< PreviousAdding A Test Case To A Test Suite.

NextNext >>>

Prev<<< PreviousExtending DejaGnu

Chapter 4. Extending DejaGnu

NextNext >>>

Prev<<< PreviousNextNext >>> Adding A New Target

Prev<<< PreviousExtending DejaGnu

Chapter 4. Extending DejaGnu

NextNext >>>

Prev<<< PreviousNextNext >>> Adding A New Tool

Prev<<< PreviousExtending DejaGnu

Chapter 4. Extending DejaGnu

NextNext >>>

file. This will add all the Makefile support needed to run DejaGnu, and support the Make CheckMake Check target.

, to set up the Tcl copies of configuration-dependent values. This is called the Local Config FileLocal Config File The check target must run the

Example 4-1. Sample Makefile.in FragmentExample 1. Sample Makefile.in Fragment

Example 4-2. Simple Batch Program Tool Init FileExample 2. Simple Batch Program Tool Init File

Example 4-3. Simple Interactive Program Tool Init FileExample 3. Simple Interactive Program Tool Init File

Example 4-4. Testing A New Tool ConfigExample 4. Testing A New Tool Config

Example 4-5. Example Test Case RunExample 5. Example Test Case Run

Prev<<< PreviousBoard Config File

NextNext >>>

Prev<<< PreviousCustomizing DejaGnu

Chapter 3. Customizing DejaGnu

NextNext >>>

Adding A New BoardAdding A New Board chapter.

An example board config file for a GNU simulator is as @@ -98,9 +104,12 @@ CLASS="EMPHASIS" is part of your build tree.

Example 3-5. Board Config FileExample 5. Board Config File

. These return the proper flags to compiler and link an executable image using LibglossLibgloss, the GNU BSP (Board Support Package). The final procedures are Prev<<< PreviousBoard Config File Values

NextNext >>>

Prev<<< PreviousExtending DejaGnu

Chapter 4. Extending DejaGnu

NextNext >>>

Table 4-1. Common Board Info FieldsTable 1. Common Board Info Fields Description Additional link flags, rarely used.

Description
Additional link flags, rarely used.

@@ -341,13 +359,20 @@ VALIGN="TOP" > Table 4-2. Board Info Fields For GCC & GDBTable 2. Board Info Fields For GCC & GDB Description @@ -839,7 +867,7 @@ ALIGN="left" VALIGN="top" >Prev<<< PreviousNextNext >>> DejaGnuThe GNU Testing FrameworkRob SavoyeRob Savoye Copyright © 2001 by Free Software Foundation, Inc. Copyright © 2002 by Free Software Foundation, Inc. New release Abstract1. Overview 2. Getting DejaGnu up and running Test your installation Windows Getting the source code for the calc example Create a minimal project, e.g. calc A simple project without the GNU autotools Using autoconf/autoheader/automake Our first automated tests Running the test for the calc example The various config files or how to avoid warnings When trouble strikes Testing “Hello world” locally A first remote test Setup telnet to your own host A test case for login via telnet Remote testing “Hello world” Transferring files from/to the target Preparing for crosscompilation Remote testing of calc Using WindowsNT as host and vxWorks as target Running Tests 3. Customizing DejaGnu 4. Extending DejaGnu 5. Unit Testing What Is Unit Testing ? The dejagnu.h Header File Reference Unit Testing API C Unit Testing API Pass Function Fail Function Untested Function Unresolved Function Totals Function C++ Unit Testing API Pass Method Fail Method Untested Method Unresolved Method Totals Method

NextNext >>> Builtin ProceduresPrev<<< PreviousReferenceChapter 5. Reference NextNext >>> mail_filemail_file(file to subject(file to subject); open_logsopen_logs((); close_logsclose_logs((); isbuildisbuild(pattern(pattern); is_remoteis_remote(board(board); . is3wayis3way((); ishostishost(pattern(pattern); istargetistarget(args(args); . isnativeisnative((); unknownunknown(args(args); clone_outputclone_output(message(message); reset_varsreset_vars((); log_and_exitlog_and_exit((); log_summarylog_summary(args(args); cleanupcleanup((); Config File Values Warning Warning you must clear the expected failure after using setup_xfail in a test case. Any call to setup_xfailsetup_xfail(config(config - bugidbugid); record_testrecord_test(type(type - messagemessage - argsargs); . passpass(string(string); . failfail(string(string); . xpassxpass(string(string); . xpassxpass(string(string); . set_warning_thresholdset_warning_threshold(threshold(threshold); . get_warning_thresholdget_warning_threshold((); warningwarning(string(string - numbernumber ); perrorperror(string(string - numbernumber ); . notenote(string(string); untesteduntested(string(string); unresolvedunresolved(string(string); , appending the argument string. unsupportedunsupported(string(string); init_testcountsinit_testcounts((); incr_countincr_count(name(name - argsargs); . transformtransform(toolname(toolname); check_conditional_xfailcheck_conditional_xfail(message(message - targetstargets - includesincludes - excludesexcludes); Example 5-1. Specifying the conditional xfail dataExample 1. Specifying the conditional xfail data . clear_xfailclear_xfail(config(config); -log argument to cause string to always - be added to the log file, even if it won't be printed. Use the - optional -x argument to log the test results into + a parsable XML file. Use the optional -n argument to print string without a - trailing newline. Use the optional argument + to print string without a trailing newline. Use the optional + -- argument if - string begins with "-". argument if string begins with "-". verboseverbose(-log(-log + -x - -n-n - -r-r - stringstring - numbernumber); -x -log load_libload_lib(filespec(filespec); call_remotecall_remote(type(type - procproc - destdest - argsargs); check_for_board_statuscheck_for_board_status(variable(variable); file_on_buildfile_on_build(op(op - filefile - argsargs); file_on_hostfile_on_host(op(op - filefile - argsargs); local_exec(commandlinelocal_exec(commandline - inpinp - outpoutp - timeouttimeout); remote_binaryremote_binary(host(host); remote_closeremote_close(shellid(shellid); remote_downloadremote_download(dest(dest - filefile - argsargs); remote_execremote_exec(hostname(hostname - programprogram - argsargs); remote_expectremote_expect(board(board - timeouttimeout - argsargs); remote_fileremote_file(dest(dest - argsargs); remote_ldremote_ld(dest(dest - progprog); remote_loadremote_load(dest(dest - progprog - argsargs); remote_openremote_open(type(type); remote_pop_connremote_pop_conn(host(host); remote_push_connremote_push_conn(host(host); remote_raw_binaryremote_raw_binary(host(host); remote_raw_closeremote_raw_close(host(host); remote_raw_fileremote_raw_file(dest(dest - argsargs); remote_raw_ldremote_raw_ld(dest(dest - progprog); remote_raw_loadremote_raw_load(dest(dest - progprog - argsargs); remote_raw_openremote_raw_open(args(args); remote_raw_sendremote_raw_send(dest(dest - stringstring); remote_raw_spawnremote_raw_spawn(dest(dest - commandlinecommandline); remote_raw_transmitremote_raw_transmit(dest(dest - filefile); remote_raw_waitremote_raw_wait(dest(dest - timeouttimeout); remote_rebootremote_reboot(host(host); remote_sendremote_send(dest(dest - stringstring); remote_spawnremote_spawn(dest(dest - commandlinecommandline - argsargs); remote_swap_connremote_swap_conn(host(host); remote_transmitremote_transmit(dest(dest - filefile); remote_uploadremote_upload(dest(dest - srcfilesrcfile - argarg); remote_waitremote_wait(dest(dest - timeouttimeout); standard_closestandard_close(host(host); standard_downloadstandard_download(dest(dest - filefile - destfiledestfile); standard_execstandard_exec(hostname(hostname - argsargs); standard_filestandard_file(dest, op, args(destopargs); standard_loadstandard_load(dest(dest - progprog - argsargs); standard_rebootstandard_reboot(host(host); standard_sendstandard_send(dest(dest - stringstring); standard_spawnstandard_spawn(dest(dest - commandlinecommandline); standard_transmitstandard_transmit(dest(dest - filefile); standard_uploadstandard_upload(dest srcfile destfile(dest srcfile destfile); standard_waitstandard_wait(dest(dest - timeouttimeout); unix_clean_filenameunix_clean_filename(dest(dest - filefile); telnettelnet(hostname(hostname - portport); rloginrlogin(hostname(hostname); rshrsh(hostname(hostname); tiptip(port(port); kermitkermit(port(port - bpsbps); kermit_openkermit_open(dest(dest - argsargs); kermit_commandkermit_command(dest(dest - argsargs); kermit_sendkermit_send(dest string args(dest string args); kermit_transmitkermit_transmit(dest(dest - filefile - argsargs); telnet_opentelnet_open(hostname(hostname - argsargs); telnet_binarytelnet_binary(hostname(hostname); telnet_transmittelnet_transmit(dest(dest - filefile - argsargs); tip_opentip_open(hostname(hostname); rlogin_openrlogin_open(arg(arg); rlogin_spawnrlogin_spawn(dest(dest - cmdlinecmdline); rsh_openrsh_open(hostname(hostname); rsh_downloadrsh_download(desthost(desthost - srcfilesrcfile - destfiledestfile); rsh_uploadrsh_upload(desthost(desthost - srcfilesrcfile - destfiledestfile); rsh_execrsh_exec(boardname(boardname - cmdcmd - argsargs); ftp_openftp_open(host(host); ftp_uploadftp_upload(host(host - remotefileremotefile - localfilelocalfile); ftp_downloadftp_download(host(host - localfilelocalfile - remotefileremotefile); ftp_closeftp_close(host(host); tip_downloadtip_download(spawnid(spawnid - filefile); default_linkdefault_link(board(board - objectsobjects - destfiledestfile - flagsflags); default_target_assembledefault_target_assemble(source(source - destfiledestfile - flagsflags); default_target_compiledefault_target_compile(source(source - destfiledestfile - typetype - optionsoptions); pop_configpop_config(type(type); prune_warningsprune_warnings(text(text); push_buildpush_build(name(name); push_configpush_config(type(type - namename); reboot_targetreboot_target((); target_assembletarget_assemble(source destfile flags(source destfile flags); target_compiletarget_compile(source(source - destfiledestfile - typetype - optionsoptions); board_infoboard_info(machine(machine - opop - argsargs); host_infohost_info(op(op - argsargs); set_board_infoset_board_info(entry(entry - valuevalue); set_currtarget_infoset_currtarget_info(entry(entry - valuevalue); target_infotarget_info(op(op - argsargs); unset_board_infounset_board_info(entry(entry); unset_currtarget_infounset_currtarget_info(entry(entry); push_targetpush_target(name(name); This unsets the current target connection. pop_targetpop_target((); list_targetslist_targets((); push_hostpush_host(name(name); This unsets the current host connection. pop_hostpop_host((); . compilecompile(file(file); . archivearchive(file(file); ranlibranlib(file(file); execute_anywhereexecute_anywhere(cmdline(cmdline); ${tool}_start${tool}_start((); . ${tool}_load${tool}_load((); . ${tool}_exit${tool}_exit((); ${tool}_version${tool}_version((); getdirsgetdirs(rootdir(rootdir - patternpattern); findfind(rootdir(rootdir - patternpattern); . whichwhich(file(file); .) grepgrep(filename(filename - regexpregexp - --line--line); pruneprune(list(list - patternpattern); slayslay(name(name); absoluteabsolute(path(path); . psourcepsource(file(file); runtests - is a list of two elements. The first is the pathname of the - testsuite expect script running. The second is a copy of what was on + is a list of two elements. The first is a copy of what was on the right side of the = if +> if " was specified, or - an empty string if no such argument is present. This is used by tools - like compilers where each testcase is a file. runtest_file_pruntest_file_p(runtests(runtests - testcasetestcase); The pathname of the testsuite expect script - running The list of patterns to compare against. + diffdiff(file_1(file_1 - file_2file_2); . setenvsetenv(var(var - valval); . unsetenvunsetenv(var(var); getenvgetenv(var(var); prune_system_crudprune_system_crud(system(system - testtest); libgloss_link_flagslibgloss_link_flags(args(args); libgloss_include_flagslibgloss_include_flags(args(args); newlib_link_flagsnewlib_link_flags(args(args); newlib_include_flagsnewlib_include_flags(args(args); libio_include_flagslibio_include_flags(args(args); libio_link_flagslibio_link_flags(args(args); g++_include_flagsg++_include_flags(args(args); g++_link_flagsg++_link_flags(args(args); libstdc++_include_flagslibstdc++_include_flags(args(args); libstdc++_link_flagslibstdc++_link_flags(args(args); get_multilibsget_multilibs(args(args); find_binutils_progfind_binutils_prog(name(name); find_gccfind_gcc((); find_gcjfind_gcj((); find_g++find_g++((); find_g77find_g77((); process_multilib_optionsprocess_multilib_options(args(args); add_multilib_optionadd_multilib_option(args(args); find_gasfind_gas((); find_ldfind_ld((); build_wrapperbuild_wrapper(gluefile(gluefile); winsup_include_flagswinsup_include_flags(args(args); winsup_link_flagswinsup_link_flags(args(args); . dumpvarsdumpvars(vars(vars); . dumplocalsdumplocals(args(args); . dumprocsdumprocs(pattern(pattern); . dumpwatchdumpwatch(pattern(pattern); watcharraywatcharray(element(element - typetype); watchvarwatchvar(var(var - typetype); . watchunsetwatchunset(arg(arg); . watchwritewatchwrite(var(var); . watchreadwatchread(var(var); . watchdelwatchdel(args(args); . printprint(var(var); . quitquit((); Prev<<< Previous NextNext >>> Prev<<< PreviousCustomizing DejaGnuChapter 3. Customizing DejaGnu NextNext >>> In the user editable second section of the Personal Config FilePersonal Config File you can not only override the configuration variables captured in the first section, but also specify default values for all on the site.exp. Invoking RuntestInvoking Runtest, for explanations of the command-line options. Table 3-1. Tcl Variables For Command Line OptionsTable 1. Tcl Variables For Command Line Options description Email the output log to the specified address. @@ -418,9 +432,12 @@ CLASS="FILENAME" > file looks like: Example 3-12. Personal Config FileExample 12. Personal Config File Prev<<< Previous +C++ Unit Testing API NextNext >>> DejaGnu: The GNU Testing Framework <<< Previous Unit Testing API C++ Unit Testing API All of the methods that take a + msg parameter use a C char * + or STL string, that is the message to be + dislayed. There currently is no support for variable + length arguments. Pass Method This prints a message for a successful test + completion. TestState::pass(msg); Fail Method This prints a message for an unsuccessful test + completion. TestState::fail(msg); Untested Method This prints a message for an test case that isn't run + for some technical reason. TestState::untested(msg); Unresolved Method This prints a message for an test case that is run, + but there is no clear result. These output states require a + human to look over the results to determine what happened. + TestState::unresolved(msg); Totals Method This prints out the total numbers of all the test + state outputs. TestState::totals(); <<< Previous Home Unit Testing API Up \ No newline at end of file diff --git a/doc/overview/customizing.html b/doc/overview/customizing.html index 2ae04c4..b756ab0 100644 --- a/doc/overview/customizing.html +++ b/doc/overview/customizing.html @@ -1,10 +1,12 @@ + Customizing DejaGnuPrev<<< PreviousNextNext >>> Chapter 3. Customizing DejaGnuCustomizing DejaGnu Table of Contents Local Config File Global Config File Board Config File Remote Host Testing Config File Values The site configuration file, . Example 3-1. The first section starts withExample 1. The first section starts with Example 3-2. The first section ends with this lineExample 2. The first section ends with this line target_triplet. All other variables are tool - dependant. ie for testing a compiler, the value for + dependant, i.e., for testing a compiler, the value for CC testing. Example 3-3. Local Config FileExample 3. Local Config File Prev<<< PreviousDebugging A Test Case NextNext >>> Prev<<< PreviousExtending DejaGnuChapter 4. Extending DejaGnu NextNext >>> Prev<<< PreviousNextNext >>> Design GoalsPrev<<< PreviousOverviewChapter 1. Overview NextNext >>> permited testing interactive programs, like +>permitted testing interactive programs, like GDB permited testing batch oriented programs, like +>permitted testing batch oriented programs, like GCCPrev<<< PreviousNextNext >>> +The dejagnu.h Header File DejaGnu: The GNU Testing Framework <<< Previous Unit Testing Next >>> The dejagnu.h Header File DejaGnu uses a single header file to assist in unit + testing. As this file also produces it's one test state output, + it can be run standalone, which is very useful for testing on + embedded systems. This header file has a C and C++ API for the + test states, with simple totals, and standardized + output. Because the output has been standardized, DejaGnu can be + made to work with this test case, without writing almost any + Tcl. The library module, dejagnu.exp, will look for the output + messages, and then merge them into DejaGnu's. <<< Previous Home Next >>> Unit Testing Up Reference \ No newline at end of file diff --git a/doc/overview/extending.html b/doc/overview/extending.html index 904f6af..c6ce943 100644 --- a/doc/overview/extending.html +++ b/doc/overview/extending.html @@ -1,10 +1,12 @@ + Extending DejaGnuPrev<<< PreviousNextNext >>> Chapter 4. Extending DejaGnuExtending DejaGnu Table of Contents Adding A New Test Suite Adding A New Tool Adding A New Target Adding A New Board Board Config File Values Writing A Test Case Debugging A Test Case Adding A Test Case To A Test Suite. Hints On Writing A Test Case Special variables used by test cases. Prev<<< PreviousNextNext >>> File MapPrev<<< PreviousReferenceNext >>>Chapter 5. Reference lib/xsh.exp lib/dejagnu.exp Prev<<< Previous Next >>> Unit Testing API +Getting DejaGnu up and runningDejaGnu: The GNU Testing Framework <<< Previous Next >>> Getting DejaGnu up and running This chapter was originally written by Niklaus Giger (ngiger@mus.ch) because he lost a week to figure out how DejaGnu works and how to write a first test. Follow these instructions as closely a possible in order get a good insight into how DejaGnu works, else you might run into a lot of subtle problems. You have been warned. It should be no big problems installing DejaGnu using your package manager or from the source code. Under a Debian/GNU/Linux systems just type (as root) apt-get dejagnu . These examples were run on a primary machine with a AMD K6 and a Mac Powerbook G3 serving as a remote target. The tests for Windows were run under Windows NT using the actual cygwin version (1.3.x as of October 2001). It's target system was a PPC embedded system running vxWorks. Test your installation Create a new user called "dgt" (DejaGnuTest), which uses bash as it login shell. PS1 must be set to '\u:\w\$ ' in its ~/.bashrc. Login as this user, create an empty directory and change the working directory to it. e.g dgt:~$ mkdir ~/dejagnu.test +dgt:~$ cd ~/dejagnu.test Now you are ready to test DejaGnu's main program called ruuntest. The expecteted output is shown Example 1. Runtest output in a empty directory dgt:~/dejagnu.test$ runtest +WARNING: Couldn't find the global config file. +WARNING: No tool specified Test +Run By dgt on Sun Nov 25 17:07:03 2001 Native configuration is i586-pc-linux-gnu +=== tests === +Schedule of variations: unix +Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. +Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. +ERROR: Couldn't find tool config file for unix. +=== Summary === We will show you later how to get rid of all the WARNING- and ERROR-messages. The files testrun.sum and testrun.log have been created, which do not interest us at this point. Let's remove them. :~/dejagnu.test$ rm testrun.sum testrun.log Windows On Windows systems DejaGnu is part of a port of a lot of Unix tools to the Windows OS, called cygwin. Cygwin may be downloaded and installed from a mirror of http://sources.redhat.com/cygwin/. All examples were also run on Windows NT. If nothing is said, you can assume that you should get the same output as on a Unix system. You will need a telnet daemon if you want to use a WindowsNT box as a remote target. There seems to be a freeware telnet daemon at http://www.fictional.net/. Getting the source code for the calc example If you are running a Debian distribution you can find the examples under /usr/share/doc/dejagnu/examples. +These examples seem to be missing in RedHat's RPM. +In this case download the sources of DejaGnu and adjust the pathes to the DejaGnu examples accordingly. <<< Previous Home Next >>> A POSIX conforming test framework Create a minimal project, e.g. calc \ No newline at end of file diff --git a/doc/overview/global.html b/doc/overview/global.html index e3a988c..ce1f4cc 100644 --- a/doc/overview/global.html +++ b/doc/overview/global.html @@ -1,10 +1,12 @@ + Global Config FilePrev<<< PreviousCustomizing DejaGnuChapter 3. Customizing DejaGnu NextNext >>> Example 3-4. Global Config fileExample 4. Global Config file Adding A New BoardAdding A New Board chapter. The more complicated example is the one for Prev<<< PreviousHints On Writing A Test Case NextNext >>> Prev<<< PreviousExtending DejaGnuChapter 4. Extending DejaGnu NextNext >>> Prev<<< PreviousNextNext >>> InstallationPrev<<< PreviousReferenceChapter 5. Reference NextNext >>> ../dejagnu-1.4/configure +> ../dejagnu-1.4.3/configure Prev<<< PreviousNextNext >>> What's New In This ReleasePrev<<< PreviousOverviewChapter 1. Overview NextNext >>> LibglossLibgloss. Prev<<< PreviousNextNext >>> The files DejaGnu produces.Prev<<< PreviousRunning TestsChapter 2. Running Tests NextNext >>> Example 2-1. Here is a short sample summary logExample 1. Here is a short sample summary log Example 2-2. Here is a brief example showing a detailed log for +>Example 2. Here is a brief example showing a detailed log for G++ Example 2-3. The log messages begin with a message of the formExample 3. The log messages begin with a message of the form Example 2-4. Here is an excerpt from the debugging log for a +>Example 4. Here is an excerpt from the debugging log for a GDBPrev<<< Previous Overview NextNext >>> Prev<<< PreviousNextNext >>> Chapter 1. OverviewOverview Table of Contents What is DejaGnu ? What's New In This Release Design Goals A POSIX conforming test framework Prev<<< PreviousNextNext >>> A POSIX conforming test frameworkPrev<<< PreviousOverviewChapter 1. Overview NextNext >>> PASS : UNTESTED The only remaining output message left is intended to test features that are specified by the applicable POSIX standard as conditional: UNSUPPORTED DejaGnu uses the same output procedures to produce these messages for all test suites, and these procedures are already known to conform @@ -319,7 +336,7 @@ ALIGN="left" VALIGN="top" >Prev<<< PreviousNextNext >>>Running TestsGetting DejaGnu up and running AbstractPrev<<< PreviousNextNext >>> Prev<<< PreviousNextNext >>> ReferencePrev<<< PreviousNextNext >>> Chapter 5. ReferenceReference Table of Contents Obtaining DejaGnu Installation Builtin Procedures File MapPrev<<< PreviousNextNext >>>Special variables used by test cases.The dejagnu.h Header File Remote Host TestingPrev<<< PreviousCustomizing DejaGnuChapter 3. Customizing DejaGnu NextNext >>> Note: Thanks to Dj Delorie for the original paper that this section is based on. DejaGnu also supports running the tests on a remote @@ -126,9 +150,12 @@ TARGET="_top" releng's area in SV to your machine:Example 3-6. Remote host setupExample 6. Remote host setup Example 3-7. Add The Board DirectoryExample 7. Add The Board Directory Example 3-8. Setup Cross Remote TestingExample 8. Setup Cross Remote Testing Example 3-9. Setup Native Remote TestingExample 9. Setup Native Remote Testing Example 3-10. Run Test RemotelyExample 10. Run Test Remotely Example 3-11. Run a Test RemotelyExample 11. Run a Test Remotely Prev<<< PreviousRunning Tests NextNext >>> Prev<<< PreviousNextNext >>> Chapter 2. Running TestsRunning Tests Table of Contents Make check Runtest The files DejaGnu produces. There are two ways to execute a test suite. The most common way is when there is existing support in the @@ -107,9 +91,7 @@ CLASS="COMMAND" > directcly from the command line requires either all the correct options, or the Local Config FileLocal Config File must be setup correctly. Prev<<< PreviousNextNext >>>A POSIX conforming test frameworkA first remote test RuntestPrev<<< PreviousRunning TestsChapter 2. Running Tests NextNext >>> flags the outcome of each test as one of these cases. A POSIX Conforming Test FrameworkA POSIX Conforming Test Framework for a discussion of how POSIX specifies the meanings of these cases. PASS runtest may also display the following messages: ERROR Prev<<< PreviousNextNext >>> Special variables used by test cases.Prev<<< PreviousExtending DejaGnuChapter 4. Extending DejaGnu NextNext >>> $prms_id Prev<<< PreviousNextNext >>>ReferenceUnit Testing +Unit TestingDejaGnu: The GNU Testing Framework <<< Previous Next >>> Unit Testing What Is Unit Testing ? Most regression testing as done by DejaGnu is system + testing. This is the complete application is tested all at + once. Unit testing is for testing single files, or small + libraries. In this case, each file is linked with a test case in + C or C++, and each function or class and method is tested in + series, with the test case having to check private data or + global variables to see if the function or method worked. This works particularly well for testing APIs and at level + where it is easier to debug them, than by needing to trace through + the entire appication. Also if there is a specification for the + API to be tested, the testcase can also function as a compliance + test. <<< Previous Home Next >>> Special variables used by test cases. The dejagnu.h Header File \ No newline at end of file diff --git a/doc/overview/unittestapi.html b/doc/overview/unittestapi.html new file mode 100644 index 0000000..f81a32e --- /dev/null +++ b/doc/overview/unittestapi.html @@ -0,0 +1,316 @@ + +Unit Testing APIDejaGnu: The GNU Testing Framework <<< Previous Next >>> Unit Testing API C Unit Testing API All of the functions that take a + msg parameter use a C char * that is + the message to be dislayed. There currently is no support for + variable length arguments. Pass Function This prints a message for a successful test + completion. pass(msg); Fail Function This prints a message for an unsuccessful test + completion. fail(msg); Untested Function This prints a message for an test case that isn't run + for some technical reason. untested(msg); Unresolved Function This prints a message for an test case that is run, + but there is no clear result. These output states require a + human to look over the results to determine what happened. + unresolved(msg); Totals Function This prints out the total numbers of all the test + state outputs. totals(); <<< Previous Home Next >>> File Map C++ Unit Testing API \ No newline at end of file diff --git a/doc/overview/writing.html b/doc/overview/writing.html index 17e09ed..30c464a 100644 --- a/doc/overview/writing.html +++ b/doc/overview/writing.html @@ -1,10 +1,12 @@ + Writing A Test CasePrev<<< PreviousExtending DejaGnuChapter 4. Extending DejaGnu NextNext >>> Prev<<< PreviousNextNext >>> +Create a minimal project, e.g. calcDejaGnu: The GNU Testing Framework <<< Previous Getting DejaGnu up and running Next >>> Create a minimal project, e.g. calc In this section you will to start a small project, +using the sample application calc, which is part of your DejaGnu distribution A simple project without the GNU autotools The runtest program can be run standalone. All the autoconf/automake support is just cause those programs are commonly used for other GNU applications. The key to running runtest standalone is having the local site.exp file setup correctly, which automake does. The generated site.exp should like like: set tool calc +set srcdir . +set objdir /home/dgt/dejagnu.test Using autoconf/autoheader/automake We have to prepare some input file in order to run autocon and automake. There is book “GNU autoconf, automake and libtool” by Garry V. Vaughan, et al. NewRider, ISBN 1-57870-190-2 which describes this process thoroughly. From the calc example distributed with the DejaGnu documentation you should copy the program file itself (calc.c) and some additional files, which you might examine a little bit close to derive their meanings. dgt:~/dejagnu.test$ cp -r /usr/share/doc/dejagnu/examples/calc/\ +{configure.in,Makefile.am,calc.c,testsuite} . In Makemake.am note the presence of the AUTOMAKE_OPTIONS = dejagnu. This option is needed. Run aclocal to generate aclocal.m4, which is a collection of macros needed by configure.in dgt:~/dejagnu.test$ aclocal autoconf is another part of the auto-tools. +Run it to generate configure based on information contained in configure.in. dgt:~/dejagnu.test$ autoconf autoheader is another part of the auto-tools. +Run it to generate calc.h.in. dgt:~/dejagnu.test$ autoheader The Makefile.am of this example was developed as port of the DejaGnu +distribution. +Adapt Makefile.am for this test. Replace the line +“#noinst_PROGRAMS = calc” to +“bin_PROGRAMS = calc”. +Change the RUNTESTDEFAULTFLAGS from +“$$srcdir/testsuite” to +“./testsuite”. Running automake at this point contains a series of warning in its output as shown in the following example: Example 2. Sample output of automake with missing files dgt:~/dejagnu.test$ automake --add-missing +automake: configure.in: installing `./install-sh' +automake: configure.in: installing `./mkinstalldirs' +automake: configure.in: installing `./missing' +automake: Makefile.am: installing `./INSTALL' +automake: Makefile.am: required file `./NEWS' not found +automake: Makefile.am: required file `./README' not found +automake: Makefile.am: installing `./COPYING' +automake: Makefile.am: required file `./AUTHORS' not found +automake: Makefile.am: required file `./ChangeLog' not found +configure.in: 4: required file `./calc.h.in' not found +Makefile.am:6: required directory ./doc does not exist Create a empty directory doc and empty files +INSTALL, NEWS, README, AUTHORS, ChangeLog and COPYING. +The default COPYING will point to the GNU Public License (GPL). +In a real project it would be time to add some meaningfull text in each file. Adapt calc to your environment by calling configure. Example 3. Sample output of configure dgt:~/dejagnu.test$ ./configure +creating cache ./config.cache +checking whether to enable maintainer-specific portions of Makefiles... no +checking for a BSD compatible install... /usr/bin/install -c +checking whether build environment is sane... yes +checking whether make sets ${MAKE}... yes +checking for working aclocal... found +checking for working autoconf... found +checking for working automake... found +checking for working autoheader... found +checking for working makeinfo... found +checking for gcc... gcc checking whether the C compiler (gcc ) works... yes +checking whether the C compiler (gcc ) is a cross-compiler... no +checking whether we are using GNU C... yes +checking whether gcc accepts -g... yes +checking for a BSD compatible install... /usr/bin/install -c +checking how to run the C preprocessor... gcc -E +checking for stdlib.h... yes +checking for strcmp... yes +updating cache ./config.cache +creating ./config.status +creating Makefile creating calc.h If you are familiar with GNU software, +this output should not contain any surprise to you. +Any errors should be easy to fix for such a simple program. Build the calc executable: Example 4. Sample output building calc dgt:~/dejagnu.test$ make +gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -c calc.c +gcc -g -O2 -o calc calc.o You prepared a few files and then called some commands. +Respecting the right order assures a automatic and correctly compiled calc program. The following example resumes the correct order. Example 5. Creating the calc program using the GNU autotools dgt:~/dejagnu.test$ aclocal +dgt:~/dejagnu.test$ autoconf +dgt:~/dejagnu.test$ autoheader +dgt:~/dejagnu.test$ automake --add-missing +dgt:~/dejagnu.test$ ./configure +dgt:~/dejagnu.test$ make Play with calc and verify whether it works correctly. +A sample session might look like this: dgt:~/dejagnu.test$ ./calc +calc: version +Version: 1.1 +calc: add 3 4 +7 +calc: multiply 3 4 +12 +calc: multiply 2 4 +12 +calc: quit Look at the intentional bug that 2 times 4 equals 12. The tests run by DejaGnu need a file called site.exp, +which is automatically generated if we call “make site.exp”. +This was the purpose of the “AUTOMAKE_OPTIONS = dejagnu” in Makefile.am. Example 6. Sample output generating a site.exp dgt: make site.exp +dgt:~/dejagnu.test$ make site.exp +Making a new site.exp file... <<< Previous Home Next >>> Getting DejaGnu up and running Up Our first automated tests \ No newline at end of file diff --git a/doc/overview/x276.html b/doc/overview/x276.html new file mode 100644 index 0000000..ca3a1d3 --- /dev/null +++ b/doc/overview/x276.html @@ -0,0 +1,440 @@ + +Our first automated testsDejaGnu: The GNU Testing Framework <<< Previous Getting DejaGnu up and running Next >>> Our first automated tests Running the test for the calc example Now we are ready to call the automated tests Example 7. Sample output of runtest in a configured directory dgt:~/dejagnu.test$ make check +make check-DEJAGNU +make[1]: Entering directory `/home/dgt/dejagnu.test' srcdir=`cd . && pwd`; export srcdir; \ +EXPECT=expect; export EXPECT; \ runtest=runtest; \ +if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \ +$runtest --tool calc CALC=`pwd`/calc --srcdir ./testsuite ; \ +else echo "WARNING: could not find \`runtest'" 1>&2; :;\ +fi +WARNING: Couldn't find the global config file. +WARNING: Couldn't find tool init file +Test Run By dgt on Sun Nov 25 21:42:21 2001 +Native configuration is i586-pc-linux-gnu + + === calc tests === + +Schedule of variations: + unix + +Running target unix +Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. +Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. +Using ./testsuite/config/unix.exp as tool-and-target-specific interface file. +Running ./testsuite/calc.test/calc.exp ... +FAIL: multiply2 (bad match) + +=== calc Summary === + +# of expected passes 5 +# of unexpected failures 1 +/home/Dgt/dejagnu.test/calc version Version: 1.1 +make[1]: *** [check-DEJAGNU] Fehler 1 +make[1]: Leaving directory `/home/Dgt/dejagnu.test' make: *** [check-am] Fehler 2 Did you see the line “FAIL:“? The test cases for calc catch the bug in the calc.c file. Fix the error in calc.c later as the following examples assume a unchanged calc.c. Examine the output files calc.sum and calc.log. +Try to understand the testcases written in ~/dejagnu.test/testsuite/calc.test/calc.exp. +To understand Expect you might take a look at the book "Exploring Expect", +which is an excellent resource for learning and using Expect. (Pub: O'Reilly, ISBN 1-56592-090-2) +The book contains hundreds of examples and also includes a tutorial on Tcl. +Exploring Expect is 602 pages long.� The various config files or how to avoid warnings DejaGnu may be customized by each user. It first searches for a file called ~/.dejagnurc. Create the file ~/.dejagnurc and insert the following line: puts "I am ~/.dejagnurc" Rerun make check. Test whether the output contains "I am ~/.dejagnurc". +Create ~/my_dejagnu.exp and insert the following line: puts "I am ~/my_dejagnu.exp" In a Bash-Shell enter dgt:~/dejagnu.test$ export DEJAGNU=~/my_dejagnu.exp Run “make check” again. The output should not contain +“WARNING: Couldn't find the global config file.”. +Create the sub-directory lib. Create the file “calc.exp” in it and insert the following line: puts "I am lib/calc.exp" The last warning “WARNING: Couldn't find tool init file” +should not be part of the output of make check. +Create the directory ˜/boards. Create the file ˜/boards/standard.exp and insert the following line: puts "I am boards/standard.exp" If the variable DEJAGNU is still not empty then the (abbreviated) output of “make check” should look like this: Example 8. Sample output of runtest with the usual configuration files dgt:~/dejagnu.test$ make check +<...> +fi +I am ~/.dejagnurc +I am ~/my_dejagnu.exp +I am lib/calc.exp +Test Run By dgt on Sun Nov 25 22:19:14 2001 +Native configuration is i586-pc-linux-gnu + + === calc tests === +Using /home/Dgt/boards/standard.exp as standard board description\ +file for build. +I am ~/boards/standard.exp +Using /home/Dgt/boards/standard.exp as standard board description\ + file for host. +I am ~/boards/standard.exp + +Schedule of variations: + unix + +Running target unix +Using /home/Dgt/boards/standard.exp as standard board description\ + file for target. +I am ~/boards/standard.exp +Using /usr/share/dejagnu/baseboards/unix.exp as board description file\ +for target. +<...> It is up to you to decide when and where to use any of the above +mentioned config files for customizing. +This chapters showed you where and in which order the different config +files are run. When trouble strikes Calling runtest with the '-v'-flag shows you in even more details which files are searched in which order. Passing it several times gives more and more details. Example 9. Displaying details about runtest execution runtest -v -v -v --tool calc CALC=`pwd`/calc --srcdir ./testsuite Calling runtest with the '--debug'-flag logs a lot of details to dbg.log where you can analyse it afterwards. In all test cases you can temporary adjust the verbosity of information by adding the following Tcl-command: set verbose 9 Testing “Hello world” locally This test checks, whether the built-in shell command “echo Hello world” + will really write “Hello world” on the console. +Create the file ~/dejagnu.test/testsuite/calc.test/local_echo.exp. +It should contain the following lines Example 10. A first (local) test case set test "Local Hello World" +send "echo Hello World" +expect { + -re "Hello World" { pass "$test" } +} Run runtest again and verify the output “calc.log” <<< Previous Home Next >>> Create a minimal project, e.g. calc Up A first remote test \ No newline at end of file diff --git a/doc/overview/x319.html b/doc/overview/x319.html new file mode 100644 index 0000000..9958b9a --- /dev/null +++ b/doc/overview/x319.html @@ -0,0 +1,632 @@ + +A first remote testDejaGnu: The GNU Testing Framework <<< Previous Getting DejaGnu up and running Next >>> A first remote test Testing remote targets is a lot trickier especially if you are using an + embedded target +which has no built in support for things like a compiler, ftp server or a Bash-shell. +Before you can test calc on a remote target you have to acquire a few basics skills. Setup telnet to your own host The easiest remote host is usually the host you are working on. +In this example we will use telnet to login in your own workstation. +For security reason you should never have a telnet deamon running on +machine connected on the internet, as password and usernames are transmitted + in clear text. +We assume you know how to setup your machine for a telnet daemon. Next try whether you may login in your own host by issuing the +command “telnet localhost.1”. In order to be able to +distinguish between a normal session an a telnet login add the following lines to /home/dgt/.bashrc. if [ "$REMOTEHOST" ] +then + PS1='remote:\w\$ ' +fi Now on the machine a “remote” login looks like this: Example 11. Sample log of a telnet login to localhost dgt:~/dejagnu.test$ telnet localhost +Trying 127.0.0.1... +Connected to 127.0.0.1. +Escape character is '^]'. +Debian GNU/Linux testing/unstable Linux +K6Linux login: dgt +Password: +Last login: Sun Nov 25 22:46:34 2001 from localhost on pts/4 +Linux K6Linux 2.4.14 #1 Fre Nov 16 19:28:25 CET 2001 i586 unknown +No mail. +remote:~$ exit +logout +Connection closed by foreign host. A test case for login via telnet In order to define a correct setup we have add a line containing +“set target unix” either to ~/.dejagnurc or to ~/my_dejagnu.exp. +In ~/boards/standard.exp add the following four lines to define a few patterns for the DejaGnu telnet login procedure. Example 12. Defining a remote target board set_board_info shell_prompt "remote:" +set_board_info telnet_username "dgt" +set_board_info telnet_password "top_secret" +set_board_info hostname "localhost" As DejaGnu will be parsing the telnet session output for some well +known pattern the output there are a lot of things that can go wrong. +If you have any problems verify your setup: Is /etc/motd empty? Is /etc/issue.net empty? Exists a empty ~/.hushlogin? The LANG environment variable must be either empty or set to “C”. To test the login via telnet write a sample test case. +Create the file ~/dejagnu.test/testsuite/calc.test/remote_echo.exp and +add the following few lines: Example 13. DejaGnu script for logging in into a remote target puts "this is remote_echo.exp target for $target " +target_info $target +#set verbose 9 +set shell_id [remote_open $target] +set test "Remote login to $target" +#set verbose 0 +puts "Spawn id for remote shell is $shell_id" +if { $shell_id > 0 } { + pass "$test" +} else { + fail "Remote open to $target" +} In the runtest output you should find something like: Running ./testsuite/calc.test/local_echo.exp ... +Running ./testsuite/calc.test/remote_echoo.exp ... +this is remote_echo.exp target is unix +Spawn id for remote shell is exp7 Have again a look at calc.log to get a feeling how DejaGnu and expect +parse the input. Remote testing “Hello world” Next you will transform the above “hello world” example to +its remote equivalent. +This can be done by adding the following lines to our file remote_echo.exp. Example 14. A first (local) remote "Hello world" test set test "Remote_send Hello World" +set status [remote_send $target "echo \"Hello World\"\n" ] +pass "$test" +set test "Remote_expect Hello World" +remote_expect $target 5 { + -re "Hello World" { pass "$test" } +} Call make check. The output should contain +“# of expected passes 9” and “# of unexcpected failures 1”. Have a look at the procedures in /usr/share/dejagnu/remote.exp to have an overview of the offered procedures and their features. Now setup a real target. +In the following example we assume as target a PowerBook running Debian. +As above add a test user "dgt", install telnet and FTP servers. +In order to distinguish it from the host add the line +PS1='test:>' to /home/dgt/.bash_profile. +Also add a corresponding entry "powerbook" to /etc/hosts and verify that you +are able to ping, telnet and ftp to the target "powerbook". In order to let runtest run its test on the "powerbook" target change the following lines in ~/boards/standard.exp: Example 15. Board definition for a remote target set_board_info protocol "telnet" +set_board_info telnet_username "dgt" +set_board_info telnet_password "top_secret" +set_board_info shell_prompt "test:> " +set_board_info hostname "powerbook" Now call runtest again with the same arguments and verify whether all went okay by taking a close look at calc.log. Transferring files from/to the target A simple procedure like this will do the job for you: Example 16. Test script to transfer a file to a remote target set test "Remote_download" +puts "Running Remote_download" +# set verbose 9 +set remfile /home/dgt/dejagnu2 + +set status [remote_download $target /home/dgt/.dejagnurc $remfile] +if { "$status" == "" } { + fail "Remote download to $remfile on $target" +} else { + pass "$test" +} + +puts "status of remote_download ist $status" +# set verbose 0 After running runtest again, check whether the file dejagnu2 exists on the target. + +This example will only work if the rcp command works with your target. + +If you have a working FTP-server on the target you can use it by adding the +following lines to ~/boards/standard.exp: Example 17. Defining a board to use FTP as file transport set_board_info file_transfer "ftp" +set_board_info ftp_username "dgt" +set_board_info ftp_password "1234" Preparing for crosscompilation For crosscompiling you need working binutils, gcc and a base library like +libc or glib for your target. +It is beyond the scope of this document to describe how to get it working. +The following examples assume a cross compiler for PowerPC which is called linux-powerpc-gcc. Add AC_CANONICAL_TARGET in dejagnu.test/configure.in at the following location. Copy config.guess from /usr/share/automake to dejagnu.test. AM_CONFIG_HEADER(calc.h) +AC_CANONICAL_TARGET([]) +AM_INIT_AUTOMAKE(calc, 1.1) You need to run automake 2.5 or later. +Depending on your installation calling autoconf2.5 instead of autoconf is not needed. +The sequence to regenerate all files is: Example 18. Using autotools for cross development $ autoconf2.5 +$ autoheader +$ automake +$ ./configure --host=powerpc-linux --target=powerpc-linux +configure: WARNING: If you wanted to set the --build type, don't use --host. + If a cross compiler is detected then cross compile mode will be used. +checking build system type... ./config.guess: ./config.guess: No such file or directory +configure: error: cannot guess build type; you must specify one +$ cp /usr/share/automake/config.guess . +$ ./configure --host=powerpc-linux --target=powerpc-linux +configure: WARNING: If you wanted to set the --build type, don't use --host. +If a cross compiler is detected then cross compile mode will be used. \ +checking build system type... i586-pc-linux-gnu +checking host system type... powerpc-unknown-linux-gnu +<...> +checking whether we are cross compiling... yes +<...> +Configuration: +Source code location: . +C Compiler: powerpc-linux-gcc +C Compiler flags: -g -O2 Everything should be ready to recompile for the target: $ make +powerpc-linux-gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -c calc.c +powerpc-linux-gcc -g -O2 -o calc calc.o Remote testing of calc Not yet written, as I have problem getting libc6-dev-powerpc to work. Probably I first have to build my cross compiler. Using WindowsNT as host and vxWorks as target A more thorough walk-through will be written in a few weeks. In order to test the vxWorks as a target I changed boards/standards.exp to reflect my settings (IP, username, password). Then I reconfigured vxWorks to include a FTP and telnet server (using the same username/password combination ad in boards/standard.exp). With this setup and some minor modification (e.g. replacing echo by printf) in my test cases I could test my vxWorks system. It sure does not seem to be a correct setup by DejaGnu standard. For instance, it still loading /usr/share/dejagnu/baseboards/unix.exp instead of vxWorks. In any case I found that (at least under WindowsNT) I did not find out how the command line would let me override settings in my personal config files. <<< Previous Home Next >>> Our first automated tests Up Running Tests \ No newline at end of file -- cgit v1.1

<<< Previous	Home	Next >>>
A POSIX conforming test framework		Create a minimal project, e.g. calc

Rob Savoye

open_logsopen_logs(();close_logsclose_logs(();isbuildisbuild(pattern(pattern);

is_remoteis_remote(board(board);

.is3wayis3way(();ishostishost(pattern(pattern);

istargetistarget(args(args);

.isnativeisnative(();unknownunknown(args(args);

clone_outputclone_output(message(message);

reset_varsreset_vars(();log_and_exitlog_and_exit(();log_summarylog_summary(args(args);

record_testrecord_test(type(type - messagemessage - argsargs);

.passpass(string(string);

.failfail(string(string);

.xpassxpass(string(string);

.xpassxpass(string(string);

.set_warning_thresholdset_warning_threshold(threshold(threshold);

.get_warning_thresholdget_warning_threshold(();warningwarning(string(string - numbernumber );

perrorperror(string(string - numbernumber );

.notenote(string(string);

untesteduntested(string(string);

unresolvedunresolved(string(string);

, appending the argument string.unsupportedunsupported(string(string);

init_testcountsinit_testcounts(();incr_countincr_count(name(name - argsargs);

.transformtransform(toolname(toolname);

load_libload_lib(filespec(filespec);

call_remotecall_remote(type(type - procproc - destdest - argsargs);

check_for_board_statuscheck_for_board_status(variable(variable);

file_on_buildfile_on_build(op(op - filefile - argsargs);

file_on_hostfile_on_host(op(op - filefile - argsargs);

local_exec(commandlinelocal_exec(commandline - inpinp - outpoutp - timeouttimeout);

remote_binaryremote_binary(host(host);

remote_closeremote_close(shellid(shellid);

remote_downloadremote_download(dest(dest - filefile - argsargs);

remote_execremote_exec(hostname(hostname - programprogram - argsargs);

remote_expectremote_expect(board(board - timeouttimeout - argsargs);

remote_fileremote_file(dest(dest - argsargs);

remote_ldremote_ld(dest(dest - progprog);

remote_loadremote_load(dest(dest - progprog - argsargs);

remote_openremote_open(type(type);

remote_pop_connremote_pop_conn(host(host);

remote_push_connremote_push_conn(host(host);

remote_raw_binaryremote_raw_binary(host(host);

remote_raw_closeremote_raw_close(host(host);

remote_raw_fileremote_raw_file(dest(dest - argsargs);

remote_raw_ldremote_raw_ld(dest(dest - progprog);

remote_raw_loadremote_raw_load(dest(dest - progprog - argsargs);

remote_raw_openremote_raw_open(args(args);

remote_raw_sendremote_raw_send(dest(dest - stringstring);

remote_raw_spawnremote_raw_spawn(dest(dest - commandlinecommandline);

remote_raw_transmitremote_raw_transmit(dest(dest - filefile);

remote_raw_waitremote_raw_wait(dest(dest - timeouttimeout);

remote_rebootremote_reboot(host(host);

remote_sendremote_send(dest(dest - stringstring);

remote_spawnremote_spawn(dest(dest - commandlinecommandline - argsargs);

remote_swap_connremote_swap_conn(host(host);

remote_transmitremote_transmit(dest(dest - filefile);

remote_uploadremote_upload(dest(dest - srcfilesrcfile - argarg);

remote_waitremote_wait(dest(dest - timeouttimeout);

standard_closestandard_close(host(host);

standard_downloadstandard_download(dest(dest - filefile - destfiledestfile);

standard_execstandard_exec(hostname(hostname - argsargs);

standard_filestandard_file(dest, op, args(destopargs);

standard_loadstandard_load(dest(dest - progprog - argsargs);

standard_rebootstandard_reboot(host(host);

standard_sendstandard_send(dest(dest - stringstring);

standard_spawnstandard_spawn(dest(dest - commandlinecommandline);

standard_transmitstandard_transmit(dest(dest - filefile);

standard_uploadstandard_upload(dest srcfile destfile(dest srcfile destfile);

standard_waitstandard_wait(dest(dest - timeouttimeout);

unix_clean_filenameunix_clean_filename(dest(dest - filefile);

telnettelnet(hostname(hostname - portport);rloginrlogin(hostname(hostname);rshrsh(hostname(hostname);

tiptip(port(port);

kermitkermit(port(port - bpsbps);

kermit_openkermit_open(dest(dest - argsargs);

kermit_commandkermit_command(dest(dest - argsargs);

kermit_sendkermit_send(dest string args(dest string args);

kermit_transmitkermit_transmit(dest(dest - filefile - argsargs);

telnet_opentelnet_open(hostname(hostname - argsargs);

telnet_binarytelnet_binary(hostname(hostname);

telnet_transmittelnet_transmit(dest(dest - filefile - argsargs);

tip_opentip_open(hostname(hostname);

rlogin_openrlogin_open(arg(arg);

`open_logsopen_logs(();`
`close_logsclose_logs(();`
`isbuildisbuild(pattern(pattern);`

`is_remoteis_remote(board(board);`

`. is3wayis3way((); ishostishost(pattern(pattern);`

`istargetistarget(args(args);`

`. isnativeisnative((); unknownunknown(args(args);`

`clone_outputclone_output(message(message);`

`reset_varsreset_vars(();`
`log_and_exitlog_and_exit(();`
`log_summarylog_summary(args(args);`

`record_testrecord_test(type(type - messagemessage` - `args`args);

`. passpass(string(string);`

`. failfail(string(string);`

`. xpassxpass(string(string);`

`. xpassxpass(string(string);`

`. set_warning_thresholdset_warning_threshold(threshold(threshold);`

`. get_warning_thresholdget_warning_threshold((); warningwarning(string(string - numbernumber );`

`perrorperror(string(string - numbernumber );`

`. notenote(string(string);`

`untesteduntested(string(string);`

`unresolvedunresolved(string(string);`

`, appending the argument string. unsupportedunsupported(string(string);`

`init_testcountsinit_testcounts(();`
`incr_countincr_count(name(name - argsargs);`

`. transformtransform(toolname(toolname);`

`load_libload_lib`(`filespec`(`filespec`);

`call_remotecall_remote(type(type - procproc` - `dest`dest - `args`args);

`check_for_board_statuscheck_for_board_status(variable(variable);`

`file_on_buildfile_on_build(op(op - filefile - argsargs`);

`file_on_hostfile_on_host(op(op - filefile` - `args`args);

`local_exec(commandlinelocal_exec(commandline - inpinp` - `outp`outp - `timeout`timeout);

`remote_binaryremote_binary(host(host);`

`remote_closeremote_close(shellid(shellid);`

`remote_downloadremote_download(dest(dest - filefile - argsargs);`

`remote_execremote_exec(hostname(hostname - programprogram - argsargs`);

`remote_expectremote_expect(board(board - timeouttimeout` - `args`args);

`remote_fileremote_file(dest(dest - argsargs`);

`remote_ldremote_ld(dest(dest - progprog`);

`remote_loadremote_load(dest(dest - progprog` - `args`args);

`remote_openremote_open(type(type);`

`remote_pop_connremote_pop_conn(host(host);`

`remote_push_connremote_push_conn(host(host);`

`remote_raw_binaryremote_raw_binary(host(host);`

`remote_raw_closeremote_raw_close(host(host);`

`remote_raw_fileremote_raw_file(dest(dest - argsargs);`

`remote_raw_ldremote_raw_ld(dest(dest - progprog);`

`remote_raw_loadremote_raw_load(dest(dest - progprog - argsargs);`

`remote_raw_openremote_raw_open(args(args);`

`remote_raw_sendremote_raw_send(dest(dest - stringstring);`

`remote_raw_spawnremote_raw_spawn(dest(dest - commandlinecommandline);`

`remote_raw_transmitremote_raw_transmit(dest(dest - filefile);`

`remote_raw_waitremote_raw_wait(dest(dest - timeouttimeout);`

`remote_rebootremote_reboot(host(host);`

`remote_sendremote_send(dest(dest - stringstring);`

`remote_spawnremote_spawn(dest(dest - commandlinecommandline - argsargs);`

`remote_swap_connremote_swap_conn(host(host);`

`remote_transmitremote_transmit(dest(dest - filefile);`

`remote_uploadremote_upload(dest(dest - srcfilesrcfile - argarg);`

`remote_waitremote_wait(dest(dest - timeouttimeout);`

`standard_closestandard_close(host(host);`

`standard_downloadstandard_download(dest(dest - filefile - destfiledestfile);`

`standard_execstandard_exec(hostname(hostname - argsargs);`

`standard_filestandard_file(dest, op, args(destopargs);`

`standard_loadstandard_load(dest(dest - progprog - argsargs);`

`standard_rebootstandard_reboot(host(host);`

`standard_sendstandard_send(dest(dest - stringstring);`

`standard_spawnstandard_spawn(dest(dest - commandlinecommandline);`

`standard_transmitstandard_transmit(dest(dest - filefile);`

`standard_uploadstandard_upload(dest srcfile destfile(dest srcfile destfile);`

`standard_waitstandard_wait(dest(dest - timeouttimeout);`

`unix_clean_filenameunix_clean_filename(dest(dest - filefile);`

`telnettelnet(hostname(hostname - portport);`
`rloginrlogin(hostname(hostname);`
`rshrsh(hostname(hostname);`

`tiptip(port(port);`

`kermitkermit(port(port - bpsbps);`

`kermit_openkermit_open(dest(dest - argsargs);`

`kermit_commandkermit_command(dest(dest - argsargs);`

`kermit_sendkermit_send(dest string args(dest string args);`

`kermit_transmitkermit_transmit(dest(dest - filefile - argsargs);`

`telnet_opentelnet_open(hostname(hostname - argsargs);`

`telnet_binarytelnet_binary(hostname(hostname);`

`telnet_transmittelnet_transmit(dest(dest - filefile - argsargs);`

`tip_opentip_open(hostname(hostname);`

`rlogin_openrlogin_open(arg(arg);`

`rlogin_spawnrlogin_spawn(dest(dest - cmdlinecmdline);`