It appears that Defensics does not allow to specify a test case timeout. Sometimes, when an anomaly happens, Defensics will stop sending new commands as it is waiting for an action from the IUT and the IUT is waiting for new commands from instrumentation server. This means that the test execution will hang like that indefinitely.
We should figure out a way to reliably get out of this situation even at a cost of a test failure. Priority is to be able to run the whole test suite.
One way to fix that could be to implement a timer in the Instrumentation Server that would trigger an action after some specified amount of time. I don't yet know what action would that be. One approach could be to retry the same commands that were triggered for that particular test case.
It appears that Defensics does not allow to specify a test case timeout. Sometimes, when an anomaly happens, Defensics will stop sending new commands as it is waiting for an action from the IUT and the IUT is waiting for new commands from instrumentation server. This means that the test execution will hang like that indefinitely.
We should figure out a way to reliably get out of this situation even at a cost of a test failure. Priority is to be able to run the whole test suite.
One way to fix that could be to implement a timer in the Instrumentation Server that would trigger an action after some specified amount of time. I don't yet know what action would that be. One approach could be to retry the same commands that were triggered for that particular test case.