Is the fixlet debugger tool outdated? If so is there any better alternatives?

[adeilson]

Hello everyone,

I have a question regarding the Fixlet Debugger.

I’ve noticed that some relevance and action script statements don’t work as expected when tested in the Fixlet Debugger, even though they work correctly when deployed through a fixlet. This made me wonder whether the tool might be outdated or no longer fully aligned with the current BigFix client capabilities.

I still find the Fixlet Debugger very useful for quickly validating simple relevance and testing use cases locally, without having to deploy content across the network. However, in several scenarios, certain properties don’t seem to be recognized at all by the debugger.

Is there any plan or intention to update or modernize the Fixlet Debugger, or is there a recommended alternative for local testing of relevance and action scripts?

Any insights or best practices would be greatly appreciated.

Thanks in advance!

[orbiton]

You need to change Evaluate with Local Client and not Fixlet Debugger.

Some of the inspectors need the actual client - it will make the response a bit slower.

[SLB]

Are you using the same version of the debugger that matches your deployment? Earlier standalone instances of the debugger may predate some of the newest inspectors so will fail. Example below from the 11.0.2 debugger attempting to evaluate the yaml inspector that was added in 11.0.5, vs running in the 11.0.6 debugger that runs as expected.

Also note that some inspectors are client only so may fail in the standalone debugger/QNA mode and you need to switch it to local client mode