Blog

TestBox v4.2 Released!

Luis Majano November 20, 2020

Spread the word

Luis Majano

November 20, 2020

Spread the word


Share your thoughts


We are excited to announce a new minor version release of TestBox version 4.2.x. To install just use CommandBox: install testbox --saveDev or to update your TestBox installation update testbox.

This release includes two important security updates just in case you have deployed TestBox or your tests to production (TESTBOX-294 and TESTBOX-293). Please note, that you should NEVER deploy TestBox and your tests to production. It is a library for development purposes and it has no purpose in being deployed to production servers.

In addition to updating your Testbox installation, you need to update any test browser files that may be in your tests folder. The current version of the Testbox test browser can be found here: https://github.com/Ortus-Solutions/TestBox/blob/development/test-browser/index.cfm

You can avoid installing testbox in production by using the install --production CommandBox command.

 

Release Notes

 

Fixed

  • TESTBOX-294 - root path in test browser not enforced (SECURITY)
  • TESTBOX-281 - request.testbox: Component ... has no accessible Member with name [$TESTID]
  • TESTBOX-290 - Turning on "Prefix serialized JSON with" in ACF causes issues in code coverage report
  • TESTBOX-293 - Force properties file to have properties extension and escape special chars (SECURITY)
 

Improvements

  • TESTBOX-291 - refactor usage of locks for debug utility in specs

Add Your Comment

Recent Entries

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026