Updated 2012-09-13 07:34:57 by ABU

Documentation  edit

http://tmml.sourceforge.net/doc/tcl/tcltest.html

http://www.tcl.tk/man/tcl8.5/TclCmd/tcltest.htm

Description  edit

The tcltest package provides the user with utility tools for writing and running tests in the Tcl test suite. It can also be used to create a customized test harness for an extension.

Tcltest is bundled into the Tcl software core distribution.

Version 2, distributed with Tcl from version 8.4, is much more flexible in the kind of matching it permits. See tcltest customMatch for some examples.

When working with tcltest, recall that the return command is not just for procedures, but can be used in scripts, such as the body of a test. See return, source, and eval for other details. The last line of a test is often return or set.

Scripts for [test] options like -setup, -body, and '--cleanup'' are evaluated in the caller's scope. This is the same rule as for other control structure commands like if or while. Any command that takes a script as an argument and controls something about how that script is evaluated can be viewed as a kind of control structure. Another aspect of the control structure behaviour of [test] is that '-constraints makes execution of other scripts conditional.

Customizing the output format of cleanupTests is not very feasible at this time, as it is used as a programmatic interface for sub-processes in [runAllTests].

Alternatives  edit

New Test Package

tcltap, a simple alternative for the small test

TTXN TclTest eXtended Notation

Running tcltest  edit

testing existing Tcl interpreter

To run the Tcl source code test suite against another installed Tcl interpreter:
tclsh all.tcl

Tutorials  edit

Installing tcltest Bryan Oakley ,2006. How to install tcltest
Getting started with tcltest by Bryan Oakley ,2006. How to use tcltest

Examples  edit

How to write tcltest result values

Your first tcltests

complex results

RHS One way to handle tests that the -result option can't handle is to do something like:
 test mytest-1.1 {
     Calling my proc should always return a list of at least length 3
 } -body {
     set result [myProc a b c d e]
     # -result can't handle {>= llength 3}, so we test it here
     expr { [llength $result] >= 3 }
 } -result {1}

Ie, perform the test for passing inside the actual test body, and have the -result be 1/0 if that test passed/failed.

[customMatch] can also be used to the same effect: Define a script that compares a an actual result with a target result. Then use [customMatch] to "register" that script for the -match option. The script should return a boolean option indicating match or no match.

Other  edit

A look at the Tcl test suite with gcov

Testimonials  edit

VI : 2003/10/02. We at [1] use Tcl (and Tk) extensively. We use Tcl for hardware testing in simulation (think multimillion-gate , multifunction asic verification). One of the major factors in our initial decision to use Tcl and our continuing to use tcl is tcltest. We use most tcltest features including constraints and are very pleased with the easy configuration of tests and the reporting. I do have gripes, but relatively minor, and since it is pure Tcl, we can change it anyways..

[tcltest is a truly great and wonderful thing. We should make a point of explaining its virtues and uses.]

A wonderful addition to this page would be instructions on how to run one particular test, using verbose mode, for the purpose of reporting test suite failures to a package developer.

DGP answers:
 make TESTFLAGS='-verbose tpse -file safe.test' test

[A Pythoneer has written an article--which CL can locate if helpful--illustrating use of PyUnit with Roman numeral conversion. In the absence of any other inspiration, maybe someone wants to steal that example ...]

RS, off page topic: See also Roman numbers for Tcl routines.

AK: Most modules in tcllib come with .test files using tcltest for regression testing.

davidw 2003/10/03: I am doing some work to improve tcltest, specifically to give it an API so that you can programmatically fetch information about the test results. I would love to hear what sorts of features you would find useful - feel free to drop me email.

disneylogic It would be useful to have a callback option, prefixed by "-command" perhaps, which appeals to an expression or proc to determine the correctness of a test. In lieu of demanding a real value to compare or abusing return codes, this would adjust 'tcltest' to perform more like SUnit [2] in the Beck testing framework [3].

I encountered this when I was trying to write a routine to do sampling without replacement and could not specify a specific result to use to compare.

If there is already some way of doing this, please, please specify it here! I waded through the man page for a bit and couldn't find anything, particularly in the usage of 'test' section.

DGP Can you provide an example of what a test would look like if there was a -command option for [test] ? Assume the reader knows nothing about either SUnit or Beck.

LV I have a programming itch and am wondering if tcltest will help me scratch this itch.

Problem: set up regression testing of a client/server command line and stdout/return code related pair of applications.

Currently, I'd love to find some help, tutorials, examples, etc. of how others are successfully doing this sort of thing with the result being test cases that are nearly trivial to read and write. I'd like to not have to teach people all of tcl before they can write new test cases. Ideally, having a half dozen or so examples should provide enough context to write additional code.

I'd also like suggestions for best practices relating to this sort of use of tcltest.

Thanks!

fermulator If a particular test spews out a bunch of debug information (i.e. 'test debug mode'), is there a way to redirect stdout, for a specific test, to /dev/null? I can't seem to find a way to hide stdout. It's basically:
test print_debug_true \
{
    Validate that when enabling "Debug Mode" in this class, that all prints
    work as expected (no errors are caught).
} \
-setup \
{
    # Enable debug mode
    $myObj setDebug true
} \
-body \
{
    # Try to run some basic methods with debug mode enabled.
    # If it fails, error out, else return PASS.
    if { [catch {$myObj doStuff} err] } \
    {
        return $err
    }
    return PASS
} \
-result {PASS}

When I run the above test, stdout on the test output gets spammed with a whack of debug information, and it "skews" the high level view of which tests are running, passing, failing, etc.