Blog

Luis Majano

April 25, 2019

Spread the word


Share your thoughts


We are excited to announce the release of TestBox version 3.0.0. To install just use CommandBox: install testbox --saveDev or to update your TestBox installation update testbox. So let's explore this release

What's New With 3.0.0

TestBox 3.0.0 is a major release. It has compatibility changes that you should be aware and lots of good feaures!

Compatibility

The major compatibility issues are the engine support removals:

  • Lucee 4.5 Support Dropped
  • Adobe ColdFusion 10 Dropped

Updating

It is easy to update, just type update testbox and you are done!

Major Features

The most notable features of this release can be found below.

Code Coverage

This has been fully documented and you can find much more information in the code coverage section.

Static Test Visualizer

The static test visualizer is basically the simple reporter but works in offline mode. This means that it will read a static TestBox results json file and create the report for it in the browser. This is incredibly useful for CI integrations and representing any TestBox results json file visually.

Location

You will find the analyzer under /test-visualizer in the root of the TestBox installation.

/test-analyzer
  + index.html (visualizer)
  + test-results.json (sample test results)

Running It

To run it all you need to do is put alongside of it a test-results.json file and then run the index.html and voila! Test Results Visualized!

Release Notes

Bugs

  • [TESTBOX-234] - bddrunner.cfm: now compiles properly on ACF
  • [TESTBOX-248] - Skip methods for given/when/then fail without `this` reference

New Features

  • [TESTBOX-236] - Add CodeCoverage Reporter to TestBox
  • [TESTBOX-239] - Update the UI for the code coverage reporting and code visualizer
  • [TESTBOX-243] - Complete UI updates for test reporters
  • [TESTBOX-245] - Static Test Visualizer

Improvements

  • [TESTBOX-237] - Update usage of htmleditformat to encodeForHTML
  • [TESTBOX-242] - Removal of old cfml engines support acf10 and lucee 4.5
  • [TESTBOX-244] - streamify the code coverage collection
  • [TESTBOX-249] - Add original method name to mocking function so it can help in debugging

Add Your Comment

Recent Entries

Inherited a CFML Application With Few Tests? Here’s Where to Start!

Inherited a CFML Application With Few Tests? Here’s Where to Start!

You need to change an application that has been running for years.

It might be a ColdFusion customer portal, a Lucee application supporting internal operations, or a CFML system your team is preparing to modernize. People depend on it, but some of its behavior lives in old tickets, scattered documentation, and the memory of whoever has supported it longest.

Now a release is approaching. You know more testing would help. The difficult part is deciding where to begin without putting every other priority on hold.

Start with one important workflow and build evidence around what it needs to do.

Explore Ortus Quality Assurance Services

Maria Jose Herrera
Maria Jose Herrera
October 27, 2026
Your ColdFusion Upgrade Passed. Did Your Business Workflows?

Your ColdFusion Upgrade Passed. Did Your Business Workflows?

The server restarted. The administrator shows the expected version. Your homepage loads, and a few familiar screens look fine.

Would you tell the business the upgrade is complete?

Consider an illustrative scenario: a customer submits an order after an upgrade. The application saves it and displays a confirmation page. But the confirmation email never arrives, and the scheduled process that sends the order to fulfillment has not completed.

From the browser, the transaction...

Maria Jose Herrera
Maria Jose Herrera
October 22, 2026