Re: Winsocket test problem
When I have problems creating Winsock scripts, I have to do the following steps:
1)Record a script. Put comments between every single step that you perform during recording. This will help make the script more readable.
2)Record a second, IDENTICAL, script to that of step 1.
3)Replay both to make sure they fail in the same place.
4)Open windiff.exe (in the LR/bin directory)
5)View the data.ws files from both scripts side by side.
6)This may help you decide what needs to be correlated.
Good Luck!
Re: Winsocket test problem
Yes, in fact I also did similar steps to find out the difference.
As a matter of fact I think the protocol what is used by the tested application is quite silly. Of course no documentation about it :)
The problem is, that between 2 executions there are some differences what I cannot solve... for example in the first execution I've got a "*" and is the second execution I've got a "G" character, and there is nothing in the packet that could explain this :) Of course in the third execution this character is (for example) az "i".
Thanks for the idea!