Skip to content
Igor Unit Testing Framework
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
procedures Add Line Number Of Failing Test Case Line Apr 24, 2019
releases Add release Mar 14, 2019
.gitlab-ci.yml Add Unit Tests For Igor 6 Apr 12, 2019
.gitmodules Doxygen filter submodule: Adjust repository URL Oct 3, 2018
License.txt Fix missing license issue Mar 21, 2017 Explain that building the documentation only works on Linux Oct 8, 2018 Raise versions Mar 13, 2019

This project aims at providing a complete set of tools for programmers for writing and maintaining unit tests.


  • Runs on Windows and MacOSX
  • Completely documented and with lots of examples
  • Includes more than ten test assertions coming in three versions
  • Allows for the arbitrary grouping of test cases
  • Easily expandable and adaptable
  • Support for executing test suites from the command line

Planned features (open for collaboration):

  • Threadsafe test assertions
  • Igor Pro help file documentation


The documentation can be found here. It contains a guided tour and an introduction to the basic structure.


Igor Pro version 6.2.0 or later


  1. Install Igor
  2. Start Igor, this will create a folder called WaveMetrics in Documents
  3. Extract the zip file into the a folder, e. g. thomas/unitTestingFramework somewhere on your disc
  4. Create a link from unitTestingFramework/procedures to Documents\WaveMetrics\Igor Pro 6 User Files\User Procedures
  5. Have a look at the manual or the example experiments

Building the documentation


The build process is fully automated using docker containers. You will need


Currently the automated build process only works on Linux.

Run make from the documentation root directory docu/:

cd docu

This will create a docker container with all the required dependencies and output the manual as pdf to docu/manual.pdf and html to the docu/sphinx/html subdirectory. The documentation is built using doxygen, a home-built awk script, breathe and sphinx.

The current documentation can be found on our website.

You can’t perform that action at this time.