Over the course of developing Integrations and Scripts, it is expected that at some point your code will cause something to break. In fact, one of the greatest features of Cortex XSOAR is to use machine learning to better time these crashes so they occur on your time off.
Printing to the War Room
Let's face it, a mountain of
This will print the statement in the War Room, where you will be able to see it. Just remember to remove these statements so you can maintain the illusion of your bug never happening.
Keep in mind that this may not appear in the War Room depending on how close the
demisto.results() statement is to the failure. To display the results before an error, you can add
sys.exit(2), which will end the process before the error is returned.
When necessary, you can look in to the server logs to determine the issue. You can use the following in your code to print information to the logs.
Will print to the logs at the "Info" level.
This will print to the logs at the "Debug" level.
Will print to the logs at the "Error" level. It also may or may not notify your co-workers of your short comings.
Sometimes when printing or using the logs is too confusing or messy you want to just use the debugger and go through the code line-by-line or breakpoint-by-breakpoint. This is where demistomock comes in. Ever noticed that all integrations in your IDE start with
This is the part where you start to understand what they are (well, at least one of them and that's good enough for now).
Cortex XSOAR is a sophisticated platform with tons of amazing features but sometimes, especially when debugging, you only want one simple command to work.
demisto as a python library has a lot of functions that are integrated with the server some examples you can see above but for our debugging we usually want to use 2 or 3 of these functions:
- We want the
demisto.params()function to return the connection details we insert into the create instance in the UI.
- We want
demisto.command()to return the name of the command we want to run.
- We want
demisto.args()to return the arguments for that command.
There could be more but the following applies to those as well.
demistomock file we can see a
params function defined:
This is what is returned if we run the Python file. We can instead fill it with the connection credentials needed to connect to our instance.
and now commands such as:
will take their information from there.
This is called mocking demisto.
We need to make sure that all Cortex XSOAR functions that are used in the functions we are testing are mocked correctly. Now we can use the debugger from the IDE or ipdb to debug the code as we would any other simple Python file!