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

Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

As we approach a stable release of BoxLang and our continued marketing reaches more folks, many have asked about its purpose. Why create a new language when the JVM ecosystem already includes established languages like Kotlin, Groovy, and Scala, to name a few.

Luis Majano
Luis Majano
December 18, 2024
ColdBox Free Tip 6 - Using Routing with Wildcard Domains!

ColdBox Free Tip 6 - Using Routing with Wildcard Domains!

ColdBox gives you the flexibility to create domain-specific routes, making it perfect for multi-tenant applications or projects that need to respond differently based on the domain or subdomain being accessed. In this tip, we’ll dive into how to use the withDomain() method to create routes that match specific domains or sub-domains.

Maria Jose Herrera
Maria Jose Herrera
December 18, 2024