Latest stable 4.5 release breaks TestBox

I’ve just applied the 4.5.4.017 “stable” patch in my dev environment
and immediately ran into an issue when trying to run some test suites
using TestBox (2.3).

For passing tests there’s no issue, but if any fail TestBox itself
throws an exception:

“Element at position [1] doesn’t exist in array”

It seems the patch has changed the way template paths in the
TagContext are given when an exception is thrown. Instead of being
absolute, they are now relative. TestBox expects these paths to be
absolute.

I expect it relates to this ticket included in the release:

https://luceeserver.atlassian.net/browse/LDEV-1036

I’ve raised a new ticket here:

https://luceeserver.atlassian.net/browse/LDEV-1076

Julian.

Julian, can you check and confirm if the TestBox 2.4 release that just came
out fixes this? I don’t know for certain, but I remember seeing an error
like that on TestBox 2.3 a while back and it being fixed on the (now
released) bleeding edge.

Thanks!

~BradOn Thursday, November 17, 2016 at 8:15:10 AM UTC-6, Julian Halliwell wrote:

I’ve just applied the 4.5.4.017 “stable” patch in my dev environment
and immediately ran into an issue when trying to run some test suites
using TestBox (2.3).

For passing tests there’s no issue, but if any fail TestBox itself
throws an exception:

“Element at position [1] doesn’t exist in array”

It seems the patch has changed the way template paths in the
TagContext are given when an exception is thrown. Instead of being
absolute, they are now relative. TestBox expects these paths to be
absolute.

I expect it relates to this ticket included in the release:

https://luceeserver.atlassian.net/browse/LDEV-1036

I’ve raised a new ticket here:

https://luceeserver.atlassian.net/browse/LDEV-1076

Julian.

Hi Brad. It’s a bug with Lucee not TestBox and I’m happy to see
Micha’s already fixed it:

https://luceeserver.atlassian.net/browse/LDEV-1076

Cheers
Julian.On 21 November 2016 at 15:40, Brad Wood <@Brad_Wood> wrote:

Julian, can you check and confirm if the TestBox 2.4 release that just came
out fixes this? I don’t know for certain, but I remember seeing an error
like that on TestBox 2.3 a while back and it being fixed on the (now
released) bleeding edge.