Re: [paho-dev] Interop test questions

[Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>]

Hi Dejan,

I've just checked in a change to address this problem, and handily, some others too :-)

Instead of serializing the socket object, I've replaced that with a sequence number, which is just the order in which the sockets are created.  This makes the test log easier to follow, and should make the tests platform independent.  The tests don't rely on any internal details of the sockets, so this solution should work fine.

Let me know what you think.

Ian

On 12/17/2014 01:18 PM, Dejan Bosanac wrote:

Hi,

I started playing with mqtt interop test suite. I ran into some problems in how we serialize socket between steps.

On my system (OSX), the socket object serialized to log file looks like

<socket.socket fd=8, family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 51240), raddr=('127.0.0.1', 1883)>

There are two problems with it:

1. it can’t be easily “matched” against results as laddr property is different on every new socket.

2. to must be put in quotes to be able to eval it

I think we need to find a better way to pass the socket object between the steps and verify it’s in proper state. I’m not sure of the proper solution yet, so just wanted to share it to start a discussion around it.

Regards
--
Dejan Bosanac
----------------------
Red Hat, Inc.
dbosanac@xxxxxxxxxx
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

-- 
Ian Craggs                          
icraggs@xxxxxxxxxx                 IBM United Kingdom
Paho Project Lead; Committer on Mosquitto