A tiny unit testing framework built as a means to learn more about unit testing in ColdFusion.
ColdFusion CSS JavaScript
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
tinytest Make sure method-name regex starts on a word-boundary to prevent fals… Oct 27, 2013
Application.cfc Minor tweaks. Apr 29, 2013
LICENSE.md Add license file. Aug 15, 2013
README.md Add link to TinyTestJS to read Readme. Oct 31, 2013
index.cfm Cleaning things up. Apr 26, 2013


Tiny Test - ColdFusion Unit Testing Framework

by Ben Nadel

Tiny Test is a ColdFusion unit testing framework that I built for personal use as a means to become more comfortable with the idea of unit testing and TDD (Test Drive Development). The feature is set is intended to be incredibly limited; and, it's meant to work with an HTML page that comes pre-packaged with the framework. You just drop it in, point it at the test specifications, and open it up in the browser.

If you want a more full-featured unit testing framework, I would suggest looking into MXUnit; it's a robust unit testing framework that has been battle-hardened for years by the ColdFusion community.

Railo Compatibility

Railo's ColdFusion engine has some settings that require you to use explicit Arguments and Variables scope references. Since I am doubtful that I can be mindful of this, I have created a separate Railo branch branch. As features are added here, they will be cherry-picked into the Railo branch to keep the two in sync.

Specs Directory

Tiny Test will look in the "specs" directory for your test cases. It will attempt to run any ColdFusion component whose name ends with, "Test.cfc". For example, the following are all valid test case file names:

  • AccountTest.cfc
  • PrimeNumberGeneratorTest.cfc
  • UserServiceTest.cfc

While Tiny Test will examine all of these ColdFusion components, it will only invoke the ones that you specify in the HTML web page served up by the Tiny Test framework.

Test Cases

Inside of your test cases, Tiny Test will attempt to invoke every public method that starts with, "test". For example, the following are all valid test method names:

  • testThatThatWorks();
  • testThatThisWorks();

Within each test case can define optional methods that run before and / or after each test method:

  • beforeTests()
  • setup()
  • teardown()
  • afterTests()

In these methods, you can reset the private variables of your test case to be "pristine" for each invocation of the provided test methods.

Each of your test cases should extend the TestCase.cfc component that ships in the specs directory. This is your bridge into the core functionality provided by Tiny Test.

  • The 'beforeTests()' method executes once before all tests
  • The 'setup()' method executes before any test case
  • The 'teardown' method executes after any test case
  • The 'afterTests()' method executes once after all tests execute, even if they produced failures or exceptions.


Each of your test methods will probably make some assertion based on the state of your components. Out of the box, Tiny Test provide only the most basic assertions:

  • assert( truthy )
  • assertTrue( truthy )
  • assertFalse( falsey )
  • assertEquals( simpleValue, simpleValue )
  • assertNotEquals( simpleValue, simpleValue )

If you want to add your own custom assertions, feel free to add them to the TestCase.cfc provided in the specs directory. Since each of your test cases extends this base component, each of your test cases will have access to the custom methods that you define within TestCase.cfc.

Inside of your custom assertions, you can make use of the private method, fail(), which is how the Tiny Test tracks exceptions:

  • fail( errorMessage )

Hopefully you've found some of this vaguely interesting.

JavaScript Version - Tiny Test JS

I have ported the Tiny Test unit testing framework (as best as possible) over to JavaScript. I call it (no surprise) Tiny Test JS. It is an AngularJS application that is loaded by RequireJS and then, subsequently, uses RequireJS to load all of the test case modules.