Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] MQTT Server Setup for Testing of MQTT clients

Just so everyone knows - we are using the m2m virtual server,, to run a second copy of Mosquitto, configured to allow the Paho client tests to run against it. It has various SSL configured ports from 18884 to 18887, and a non-SSL port at 18883.

Those ports seem not to be accessible from outside the Eclipse foundation network, which is useful in limiting random use of that server which could upset the tests.


On 07/23/2013 10:46 AM, Ian Craggs wrote:
Thanks Mike.  I didn't know - I'll look into that.

On 07/22/2013 05:13 PM, Mike Milinkovich wrote:
Just in case you didn't know this: projects can ask Webmaster to set them up their own virtual server. Might be useful for running tests.

Mike Milinkovich

On 2013-07-22, at 10:44 AM, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Thanks Roger, I'll take a look.

I think I'd still want to run some client tests against a "real" server though, and vice versa. Getting enough coverage with your technique seems likely to be to be more time-consuming than using a server we have already built. Why not use it, if we have it? What about "large" message tests, for instance, where the packet has to be written in more than one attempt (for clients/servers that don't have one thread per client)?

I'll think about it.


On 07/22/2013 02:19 PM, Roger Light wrote:
Hi Ian,

For the mosquitto tests I run a per test instance of the broker for
exactly the reasons you say - many of the tests require special
configuration. Likewise, I think that running the broker on the build
machine is a sensible option because it is not affected by
connectivity problems or by whatever else is happening on the server.

For both the broker and the client, I don't use the opposite
client/broker at all, instead generating and examining received
packets within the test itself. I find it much easier to verify what
the test is doing when a client test doesn't depend on the broker and
vice versa. I suppose for completeness I should be testing them both
together as well as these isolated tests.

You can view my client tests already because they are part of the Paho
Python repository - see the test/lib directory. I would already have
them running on eclipse hudson, but I need to request some more recent
versions of Python be installed on the build machines.



On Mon, Jul 22, 2013 at 12:56 PM, Ian Craggs
<icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi All,

Al and I have been adding tests for the Java and C clients, which are run by
Hudson build jobs (see for the C job).

For the basic MQTT tests, we have pointed the tests at, which works fine. But now we need to add SSL and failover tests (for High Availability configurations), so we need to have MQTT server setups to test

We could, along with, have SSL and HA predefined setups which can be used by the tests. Would be the right place,
or should we have specific test servers somewhere else?

Or, once we had Mosquitto contributed to Eclipse, I thought the builds for the clients and server could use each other for testing. Then the tests could configure the server as they see fit, for that test. The simplest setup would entail running the MQTT server on the build machine where the
clients were being built.

Thoughts, suggestions?


paho-dev mailing list
paho-dev mailing list
paho-dev mailing list

paho-dev mailing list

paho-dev mailing list

Back to the top