Raising a vbXML.dll (commutation) condition in TC
We have an intermittent issue that during the time the AUT is communicating with a server something happens and a VB error is raised and the application stops. I was looking at object check points and find all children. I really need the ability to see the lost packet of data and how the vbXML.dll handles this. Something is coming from the server (has an issue) through the vbXML.dll and into the AUT and this causes a problem for the AUT. Part two if this (the fix) is can TC simulate this issue for testing. We can program a recover function if we can see and reliable reproduce the issue.
In short can TC raise a vbXML.dll condition in the middle of waiting for a server reply so we can trap and recover from said condition?
Thanks for any input.
Re: Raising a vbXML.dll (commutation) condition in
TestComplete cannot emulate such errors.
Since vbXML is shipped with the source code, you can debug the library to find out the cause of the problem: