When I enable CF debugging using TestBox I get an ...
# box-productsp
paolo79
08/31/2022, 2:09 PMWhen I enable CF debugging using TestBox I get an exception related to a FusionReactor object.
It's not a problem for me, but I would like to understand if I am wrong to define something in my unit_test.
I use component extends="mxunit.framework.TestCase"
Does it happen to you too?
b
bdw429s
08/31/2022, 2:14 PM@paolo79 I think CF Debugging is showing you all errors, even ones which were caught in a try/catch
bdw429s
08/31/2022, 2:15 PMThis code is a normal check to see whether FusionReactor is installed or not
https://github.com/Ortus-Solutions/TestBox/blob/ec848e10276c68501f39bf58001bed9886623fcc/system/coverage/data/CoverageGenerator.cfc#L28-L34
bdw429s
08/31/2022, 2:16 PMWe test for the class in a try/catch and if it isn't found, code coverage is disabled.
bdw429s
08/31/2022, 2:16 PMI'm not entirely sure why the debugger is showing you even errors which were successfully handled, but it sounds annoying of for you to see them 😆
bdw429s
08/31/2022, 2:17 PMBut basically you can ignore this. There is nothing wrong with it and CF is just being a little overzealous IMO in showing it to you.
bdw429s
08/31/2022, 2:17 PMIt's a normal part of the internals of testbox to detect what's installed on the system
p
paolo79
09/01/2022, 6:57 AMThanks for your response @bdw429s. Can't this check be disabled when the coverageEnabled parameter is false?
b
bdw429s
09/01/2022, 12:54 PMPossibly, but I think it just runs on init if the cfc before the config is parsed so the check can be the safe add happen only once.
bdw429s
09/01/2022, 12:55 PMYou wouldn't have noticed or cared if the debugger wasn't showing it for some reason. 😁