Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] MQTT tests (was Re: Paho repository structure)

yeah, you're absolutely right !

I had in mind to put the Paho client tests in the same project that the client itself (still in a Maven approach), something like:

├── src
│   ├── main
│   │   └── java   <-- main sources
│   └── test
│       └── java   <-- Tests are here

Let's wait for Ian's point of view. 

On Thu, Jun 14, 2012 at 12:07 AM, andypiperuk@xxxxxxxxx <andypiperuk@xxxxxxxxx> wrote:
Guys, there's likely to be overlap here with stuff that Ian Craggs was hoping to be adding to the project, so it may be worth holding off until he can work out what that contribution might look like - in the interests of avoiding too much duplication.

Also needs consideration in terms of where in the repository "tree" protocol-compliance test suites would sit.

On Wed, Jun 13, 2012 at 12:42 PM, Nicolas DEVERGE <ndeverge@xxxxxxxx> wrote:
Thanks, I'll take a look at it !

On Wed, Jun 13, 2012 at 1:17 PM, Roger Light <roger@xxxxxxxxxx> wrote:
Hi Nicolas,

> I'd be interested to port the client side tests to the Java Paho client.
> Where should I start ?

You will find the tests in the test/lib directory of the mosquitto
repository. You would need to create a directory paho-java for
example, then duplicate all of the clients to perform what is required
for the tests - publish a retained qos0 message with the correct
topic/payload and that sort of thing. The existing code for the C, C++
and Python mosquitto clients should give you what is needed.

There aren't that many client side tests yet, it would be good to get
more so feel free to mention anything else that needs testing.


paho-dev mailing list

paho-dev mailing list

Andy Piper | Farnborough, Hampshire (UK)
blog:   |   skype: andypiperuk
twitter: @andypiper  |  images:

paho-dev mailing list

Back to the top