Blog

TestBox BDD/xUnit Testing v1.1.0 Final

Luis Majano February 12, 2014

Spread the word

Luis Majano

February 12, 2014

Spread the word


Share your thoughts

We are very happy to release our first minor patch for TestBox.  This update includes finalizations of some features but mostly tons and tons of improvements and fixes as our library matures.  For those of you who do not know about TestBox, TestBox is a next generation testing framework for ColdFusion (CFML) that is based on BDD (Behavior Driven Development) for providing a clean obvious syntax for writing tests.

It contains not only a testing framework, runner, assertions and expectations library but also integrates with MockBox for mocking and stubbing. It also supports xUnit style of testing and MXUnit compatibilities.  TestBox can be downloaded from our main downloads page and it has been also integrated into the ColdBox platform as well.

Release Notes

Bugs

  • [TESTBOX-43] - Test case names in xUnit have better definitions
  • [TESTBOX-44] - Output and mode arguments not compat with MXUnit's HTML formats
  • [TESTBOX-45] - isExpectedException fails on non-inherited specs
  • [TESTBOX-46] - ANTJunit reporter needs to build single tree suite instead of nested suites
  • [TESTBOX-51] - Some MXUnit extension assertions are missing
  • [TESTBOX-53] - makePublic() doesn't seem to work for packaged methods on compatibility mode
  • [TESTBOX-54] - mock(), getMockFactory(), setMockingframework() not implemented
  • [TESTBOX-56] - The method init was not found in component TestCase.cfc.
  • [TESTBOX-58] - toThrow() cannot match empty message & cannot match detail
  • [TESTBOX-59] - isEqual assertion returns false with two equal complex structures or arrays
  • [TESTBOX-60] - HTTP Runner in samples errors
  • [TESTBOX-61] - Samples will not run without ColdBox
  • [TESTBOX-63] - beforeEach does not fire in recursive fashion for nested suites
  • [TESTBOX-65] - expectException() doesn't work on certain use cases with annotations and method calls.
  • [TESTBOX-67] - directoryTestSuite.run() doesn't completely respect its "excludes" argument in compat mode
  • [TESTBOX-68] - TestCase.cfc doesn't have life-cycle methods on compat mode
  • [TESTBOX-71] - "Global Stats" summary does not include failures from "Global Bundle Exception" failures
  • [TESTBOX-72] - Nested empty describe blocks don't show in runner

Improvement

  • [TESTBOX-57] - Allow building of ant.properties file for ANT runner so build can fail
  • [TESTBOX-70] - Reporters improved to allow for better UI when skipping and excluding tests

Resources

Finally, TestBox is also a direct drop-replacement for MXUnit as well.  

Add Your Comment

Recent Entries

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Spring Boot developers know the pain of evaluating view technologies. Thymeleaf is great — until you need more expressiveness. FreeMarker is powerful — until the syntax fights you. What if you could write templates in a dynamic JVM language that gives you the full power of the platform, feels natural, and requires zero setup to integrate?

Meet the BoxLang Spring Boot Starter.

Luis Majano
Luis Majano
March 13, 2026
Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

The growing need to evolve legacy financial platforms safely

Many Swiss banks and financial institutions still operate important systems built on ColdFusion and CFML platforms.

These systems manage a wide range of functions, including:

  • internal banking workflows
  • reporting systems
  • client portals
  • data integration platforms
  • compliance and risk management tools

In many cases, thes...

Cristobal Escobar
Cristobal Escobar
March 13, 2026
Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Many ColdFusion environments operate in a reactive mode without realizing it.

Everything seems fine… until something breaks.

A server crashes.

Performance drops suddenly.

An integration stops working.

A security audit reveals missing patches.

At that point the response is urgent:

“Can someone help us fix this now?”

Emergency support is sometimes unavoidable. But when reactive intervention becomes the norm, it usually means something deep...

Cristobal Escobar
Cristobal Escobar
March 12, 2026