1. Automated Unit Test Package For Tcl Procedures March 25, 2017
TUnit Demonstration
Automated Unit Test Package
For Tcl Procedures
March 25, 2017

2. Requirements Java runtime level of at least 1.4 tclsh Eclipse IDE
Eclipse IDE
tclsh
Make sure to add bin directory to the path

3. Installation Extract the zipped file to the eclipse home directory
Usually C:\Program Files\eclipse

4. Verifying Installation
If eclipse is being started for the first time, a welcome screen will appear.
If an error occurs, this is usually a result of the Java runtime engine not being installed properly.

5. Verifying Installation Continued
From the Window menu, set the TUnit Preferences.
This means the installation was a success.

6. TUnit Perspective
A perspective determines the visible actions and views within a window. The TUnit
perspective has 4 views: Navigator, Namespace Explorer, Tasks, and Console. The
TUnit perspective can be opened from the upper right corner, the window menu, or
by creating a new Tcl Project.

7. New Tcl Project
Create a new Tcl Project and choose the Project name and location

8. Tcl Project Continued
The Tcl Project creates the init.tcl and global.tcl files as well as the t-unit package.

9. Namespace Explorer
Namespace Explorer looks at the tclIndex file and generates the procedure names
associated with each package. Double clicking on the procedure name will open
the file where the procedure is defined.

10. Editor
The Tcl Editor has the following features: syntax highlighting, auto indentation, and
content assistance. If other plugins are installed, *.tcl files may not use the TUnit
editor. Update the file associations preferences to use the TUnit editor.

11. TUnit Menu Within the TUnit perspective, you allowed to
create a new Tcl Package and a new Tcl File.

12. Tcl Package Create a new package within a project. The package will
include the necessary file for package and namespace declaration
and init.tcl will automatically be updated.

13. Tcl File
The Tcl File wizard only requires the file name as input. But Procedure
Parameters, Version, and Author name are also allowed and will be
automatically put into the comments within the file.

14. Sample Testing Script t-unit::assertEquals 12.34 12.34 | PASS | OK
t-unit::assertEquals "hello“ "hello” | PASS | OK
t-unit::assertEquals "hello“ "world“ | FAIL | NOT_EQUAL
t-unit::assertEquals | PASS | OK
t-unit::assertEquals 2 3 | FAIL | NOT_EQUAL
t-unit::assertEquals | PASS | OK
t-unit::assertEquals | FAIL | ARG_MISMATCH
t-unit::assertEquals TRUE TRUE | PASS | OK
t-unit::assertNotEquals TRUE FALSE | PASS | OK
t-unit::assertNotEquals “hello” “world” | PASS | OK
t-unit::assertEqualsList {1 2 3} {1 2 3} | PASS | OK
t-unit::assertEqualsArray A1 A | PASS | OK

15. Using the Test Harness # Put this file at the project level.
# Can also run more than one set of
# unit tests, i.e. make a call to
# t-unit::testHarness more than once.
# Below is a sample file; init.tcl is
# required.
source init.tcl
t-unit::testHarness t-unit/t-unittestcases.test

16. Execute TUnit Script
Right click on the TUnit Script to execute and run it.

17. Results of a TUnit Run
Once the TUnit script finishes executing, a popup window will appear
with the results of the test. In addition, the console window displays the
test results.

18. Known Issues
This plugin has not been tested on Unix or Mac systems. Please report any errors that are seen and they will be fixed accordingly.